[Bug 1846871] Re: Desktop Icons NG shell extension breaks Activities vew
The Problem is independent from the NG extension. I disabled the Ubuntu Desktop Icons extension by moving it away from /usr/share/gnome- shell/extension because i use nemo-desktop. After that the activity view is broken as described above. I use nemo-desktop the last 4 years together with gnome-shell and had no problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846871 Title: Desktop Icons NG shell extension breaks Activities vew To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845424] Re: Calamares not selecting correct timezone when connected to internet
Lubuntu 19.10 QA-install on hardware - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) I've heard of this issue many times on IRC, but first for me. I could ping my ISP using name so internet (inc. DNS) was good. (most of my installs are on dell, and usually AMD/ATI video but who knows..) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845424 Title: Calamares not selecting correct timezone when connected to internet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1845424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838555] Re: nvme-cli 1.5 in Bionic does not support Micron NVME drives
I got my act together and sponsored this bug today. Now you just need SRU approval. @mruffell, welcome to the party. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838555 Title: nvme-cli 1.5 in Bionic does not support Micron NVME drives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1838555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846918] Traceback
Exception during installation: Oct 6 03:32:38 kubuntu /plugininstall.py: Traceback (most recent call last): Oct 6 03:32:38 kubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 247, in run Oct 6 03:32:38 kubuntu /plugininstall.py: self.apt_clone_restore() Oct 6 03:32:38 kubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1466, in apt_clone_restore Oct 6 03:32:38 kubuntu /plugininstall.py: restore_cmd, preexec_fn=install_misc.debconf_disconnect) Oct 6 03:32:38 kubuntu /plugininstall.py: File "/usr/lib/python3.7/subprocess.py", line 347, in check_call Oct 6 03:32:38 kubuntu /plugininstall.py: raise CalledProcessError(retcode, cmd) Oct 6 03:32:38 kubuntu /plugininstall.py: subprocess.CalledProcessError: Command '['apt-clone', 'restore-new-distro', '/target/ubiquity-apt-clone/apt-clone-state-kubuntu.tar.gz', 'eoan', '--destination', '/target']' returned non-zero exit status 1. Oct 6 03:32:38 kubuntu /plugininstall.py: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846918 Title: Ubiquity crashes near the end of installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1846918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839214] Re: Setting vm.overcommit_kbytes = 0 made the entire system explode.
[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/1839214 Title: Setting vm.overcommit_kbytes = 0 made the entire system explode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839216] Re: xenial VM hangs copying block device
[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/1839216 Title: xenial VM hangs copying block device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724370] Re: NVME model does not show up
[Expired for udisks2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: udisks2 (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/1724370 Title: NVME model does not show up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1724370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724370] Re: NVME model does not show up
[Expired for gnome-disk-utility (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-disk-utility (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/1724370 Title: NVME model does not show up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1724370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846918] Re: Ubiquity crashes near the end of installation
Exception during installation: Oct 6 03:32:38 kubuntu /plugininstall.py: Traceback (most recent call last): Oct 6 03:32:38 kubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 247, in run Oct 6 03:32:38 kubuntu /plugininstall.py: self.apt_clone_restore() Oct 6 03:32:38 kubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1466, in apt_clone_restore Oct 6 03:32:38 kubuntu /plugininstall.py: restore_cmd, preexec_fn=install_misc.debconf_disconnect) Oct 6 03:32:38 kubuntu /plugininstall.py: File "/usr/lib/python3.7/subprocess.py", line 347, in check_call Oct 6 03:32:38 kubuntu /plugininstall.py: raise CalledProcessError(retcode, cmd) Oct 6 03:32:38 kubuntu /plugininstall.py: subprocess.CalledProcessError: Command '['apt-clone', 'restore-new-distro', '/target/ubiquity-apt-clone/apt-clone-state-kubuntu.tar.gz', 'eoan', '--destination', '/target']' returned non-zero exit status 1. Oct 6 03:32:38 kubuntu /plugininstall.py: ** Tags added: installer-crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846918 Title: Ubiquity crashes near the end of installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1846918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724370] Re: NVME model does not show up
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (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/1724370 Title: NVME model does not show up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1724370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838179] Re: gnome-system-monitor snap segfaults
[Expired for gnome-system-monitor (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-system-monitor (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/1838179 Title: gnome-system-monitor snap segfaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1838179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839208] Re: Upgrade from 16.04 to 18.04 failed.
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (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/1839208 Title: Upgrade from 16.04 to 18.04 failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1839208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04
My M185 didn't register middle-click (bottom 2) neither, after trick #91, sometimes middle-click registered as bottom 4, mostly 2, and sometimes nothing, with a similar experience to #99. So I repeated #91 and ran `xinput set-button-map 4 1 2 3 2 2` and for now everything is working and solid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581088 Title: Middle mouse (wheel-click) button stopped working after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757902] Re: Please port your package away from Qt 4
** Changed in: v4l2ucp (Debian) 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/1757902 Title: Please port your package away from Qt 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l2ucp/+bug/1757902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846918] [NEW] Ubiquity crashes near the end of installation
Public bug reported: Installing Kubuntu 19.10 Beta. I believe this also happened with Kubuntu 19.04, though I don't recall clearly. The computer is a Lenovo Thinkpad X250. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubiquity 19.10.12 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.419 CurrentDesktop: KDE Date: Sat Oct 5 22:34:52 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan kubuntu ubiquity-19.10.12 ** Attachment added: "/var/log/syslog" https://bugs.launchpad.net/bugs/1846918/+attachment/5294664/+files/syslog.txt -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to ubiquity in Ubuntu. https://bugs.launchpad.net/bugs/1846918 Title: Ubiquity crashes near the end of installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1846918/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1846918] Re: Ubiquity crashes near the end of installation
** Attachment added: "/var/log/partman" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1846918/+attachment/5294673/+files/partman.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846918 Title: Ubiquity crashes near the end of installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1846918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769341] Re: Can't find HDMI
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (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/1769341 Title: Can't find HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1769341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181666]
Can anyone still reproduce this in 3.34? (3.28 or 3.30 are not supported anymore.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181666]
This happens to me several times a day and really disrupts my workflow. Please let me know what information I can add to help triage this bug. Ubuntu 18.04.3 GNOME 3.28.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845704] Re: HDMI monitor is not detected as sound output device starting from kernel 4.18.0-21 and above, Ubuntu 18.10 and 19.04
This isn't x86 specific, ppc64el is similarly affected ** Tags removed: amd64 cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845704 Title: HDMI monitor is not detected as sound output device starting from kernel 4.18.0-21 and above, Ubuntu 18.10 and 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680155] Re: mate-panel shows up in plank dock
*** This bug is a duplicate of bug 1666201 *** https://bugs.launchpad.net/bugs/1666201 What I did was to go into panel preferences and under "Behaviour" turn off "Show Unpinned". No more panel icon in plank. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680155 Title: mate-panel shows up in plank dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1680155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846914] Re: kglobalaccel5 crashed with SIGABRT in QMessageLogger::fatal()
*** This bug is a duplicate of bug 1832701 *** https://bugs.launchpad.net/bugs/1832701 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1832701, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1846914/+attachment/5294654/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1846914/+attachment/5294656/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1846914/+attachment/5294659/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1846914/+attachment/5294660/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1846914/+attachment/5294661/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1846914/+attachment/5294662/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1846914/+attachment/5294663/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1832701 kglobalaccel5 crashed with SIGABRT in raise() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846914 Title: kglobalaccel5 crashed with SIGABRT in QMessageLogger::fatal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kglobalaccel/+bug/1846914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827822] Re: kernel null pointer dereference
A month or so after reporting this, amid a frustrating series of unpredictable lockups, I figured out how to run memtest which indicated I had a bad memory card. Since replacing it, I have had no further problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827822 Title: kernel null pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845828]
The change was reverted by this commit: https://git.xfce.org/xfce/xfdesktop/commit/?id=78d841b96ce49e0427ceaa486904a529858da0bd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845828 Title: Timeout error while renaming a file To manage notifications about this bug go to: https://bugs.launchpad.net/xfdesktop/+bug/1845828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770044]
Created attachment 123034 New crash information added by DrKonqi plasmashell (5.16.5) using Qt 5.12.3 - What I was doing when the application crashed: Usually after printing Plasma would crash but restarting from terminal using killall plasmashell followed by kstart plasmashell would work, now it just keeps on crashing, so it becomes unusable. - Unusual behavior I noticed: Whenever printing succeeded, plasma would crash but resume. If printing failed and job stayed in printing queue, plasma would crash and never resume. Manual restart of plasma would be necessary. This is no longer working. -- Backtrace (Reduced): #6 0x7f6ae18e9c80 in JobModel::updateJob(int, KCupsJob const&) () at /usr/lib/x86_64-linux-gnu/libkcupslib.so #7 0x7f6ae18ebe68 in JobModel::insertJob(int, KCupsJob const&) () at /usr/lib/x86_64-linux-gnu/libkcupslib.so #8 0x7f6ae18ec46b in JobModel::getJobFinished(KCupsRequest*) () at /usr/lib/x86_64-linux-gnu/libkcupslib.so #9 0x7f6b32e203e2 in QObject::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f6b3474d65c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770044 Title: plasmashell crashes on login - so I can't use my desktop system. To manage notifications about this bug go to: https://bugs.launchpad.net/print-manager/+bug/1770044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839290] Re: systemd doesn't restart a service after crashes
** Changed in: systemd (Ubuntu) Status: Fix Committed => 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/1839290 Title: systemd doesn't restart a service after crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1839290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846842] Re: the upgrade tool from 19.04 to 19.10 failed badly
No sorry Grizzly, my prior comment was TRIAGE related... and for any subsequent reader. It was my thoughts on bug from your upgrade log and not directed to you, but any future reader. The added and now deprecated KDE/Qt package was added at some prior time to your system which was 1 of the 3 issues I saw. That package is not available in 19.10; KDE used Qt4 in 14.04 and both Qt4/Qt5 in 14.10. You probably installed a Qt based app that pulled the package in. The other two issues were non-Ubuntu sourced packages I concluded. These are NOT bugs in the Ubuntu code, but packaging issues created by 3rd parties who don't follow Ubuntu packaging versioning rules. 3rd parties usually don't consider release-upgrade time, just the release they initially package for. Only the Qt4 package issue could be bug related was my 2c. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846842 Title: the upgrade tool from 19.04 to 19.10 failed badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1846842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844021] Re: Suspend stopped working from 4.4.0-157 onwards
Thanks, but when I went to test it couldn't get this installed. Is it possibly a corrupted deb file? When I tried the linux-modules deb, I got this (Reading database ... 221473 files and directories currently installed.) Preparing to unpack linux-modules-4.15.0-66-generic_4.15.0-66.75~lp1844021_amd64.deb ... Unpacking linux-modules-4.15.0-66-generic (4.15.0-66.75~lp1844021) ... dpkg-deb (subprocess): cannot copy archive member from 'linux-modules-4.15.0-66-generic_4.15.0-66.75~lp1844021_amd64.deb' to decompressor pipe: unexpected end of file or stream dpkg-deb (subprocess): decompressing archive member: lzma error: unexpected end of input dpkg-deb: error: subprocess returned error exit status 2 dpkg: error processing archive linux-modules-4.15.0-66-generic_4.15.0-66.75~lp1844021_amd64.deb (--install): cannot copy extracted data for './lib/modules/4.15.0-66-generic/kernel/drivers/scsi/qla2xxx/qla2xxx.ko' to '/lib/modules/4.15.0-66-generic/kernel/drivers/scsi/qla2xxx/qla2xxx.ko.dpkg-new': unexpected end of file or stream Errors were encountered while processing: linux-modules-4.15.0-66-generic_4.15.0-66.75~lp1844021_amd64.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844021 Title: Suspend stopped working from 4.4.0-157 onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846127] Re: xenial/linux-hwe-edge: 4.15.0-66.75~16.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1846130 packages: meta: linux-meta-hwe-edge phase: Signoff phase-changed: Friday, 04. October 2019 00:25 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846127 Title: xenial/linux-hwe-edge: 4.15.0-66.75~16.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836823] Re: python-acme will break on November 1st
Also Brad - Regarding: * The ndg-httpsclient and pyasn1 dependency should be added back. * The idna dependency should be removed. Let me know if this is required to maintain functionality, I'd like to keep the diff for the SRU as simple as possible. If this is a change that is desirable to better reflect the ongoing direction of the project, I'm happy to address in the PPA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836823 Title: python-acme will break on November 1st To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-acme/+bug/1836823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846911] Re: DRM failed to idle channel 0
I would greatly appreciate your help, since I could not solve it by searching forums -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846911 Title: DRM failed to idle channel 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1846911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846911] [NEW] DRM failed to idle channel 0
Public bug reported: I try to install ubuntu 18.4.03LTS on my PC, the command lines are displayed at start-up, throw the error: 56.464252 nouveau :: DRM failed to idle channel 0 DRM and then shut down. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-23-generic 5.0.0-23.24~18.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 5 23:35:32 2019 LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846911 Title: DRM failed to idle channel 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1846911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836823] Re: python-acme will break on November 1st
Hi Andreas, Follow on from our IRC conversation, I've revisited and fixed the Xenial branch. Thank you for such a thorough review, and for catching those mistakes. What we're seeing here are simply mistakes on my behalf, when working to move my patches to Salsa - the debdiffs were generated at this point also. So I appreciate your work to validate and test the provided branches and diffs. I've addressed the Xenial case but also your feedback on the Bionic and Disco branches. The intention here was indeed to try and keep the branches similar to reduce backport-burden, however I can see the value in more tightly specifying the debhelper version also, so I've updated that and fixed the consistency mistakes around version (compat vs control vs changelog). Hi Brad, Thanks for jumping in again and adding more context around the upstream testing that has occurred around older versions. I had alluded to this backwards compatibility testing in my IRC conversation with Andreas, so the additional detail is very helpful. Now, to the changes I have made, and the testing I have no done and re-done: - Xenial: changelog has been updated to reflect the changes to the python dependency versions - Xenial: requirement for python(3)-cryptography packages have been lowered to 1.2.3 - Xenial: requirement for python(3)-idna packages have been lowered to 2.0 - Xenial: debhelper version has been made consistent between changelog, control and compat (v9) - Bionic: debhelper version has been returned to the original 11 in control, compat and changelog - Disco: debhelper version has been returned to the original 11 in control, compat and changelog And, to the testing I have performed on the updated branches: - Xenial: Full clean rebuild of the package from the current ubuntu-xenial branch [0] of my salsa repo, this was successful with the changes above, and the test suite runs successfully. - Xenial: I took the built package and updated one of my servers running Xenial which uses Certbot to managed TLS certificates. I was able to, using the distro packages (no PPA) upgrade successfully to the backported package, and execute a renewal against the test ACME endpoint. This successfully renewed and the debug log shows the v2 endpoint being used successfully. - Bionic: Full clean rebuild of the package from the ubuntu-bionic branch of my salsa repo [1], and the test suite ran successfully - Disco: Full clean rebuild of the package from the ubuntu-disco branch of my salsa repo [2], and the test suite ran successfully Please let me know if any further changes or testing is required. I believe I have addressed the feedback raised so far and have tested each change, but if I've missed anything, let me know. [0] https://salsa.debian.org/ec0-guest/acme/tree/ubuntu-xenial [1] https://salsa.debian.org/ec0-guest/acme/tree/ubuntu-bionic [2] https://salsa.debian.org/ec0-guest/acme/tree/ubuntu-disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836823 Title: python-acme will break on November 1st To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-acme/+bug/1836823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846871] Re: Desktop Icons NG shell extension breaks Activities vew
The extension ID is supposed to be unique. It is a serious bug if NG is using the same extension ID as an existing extension. I imagine the maintainers of extensions.gnome.org would remove an extension for that issue if it was reported. Until that bug is fixed, I don't think Ubuntu has any responsibility to attempt to block the broken extension. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846871 Title: Desktop Icons NG shell extension breaks Activities vew To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846123] Re: xenial/linux-azure: 4.15.0-1061.66 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1846131 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Signoff phase-changed: Thursday, 03. October 2019 23:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1846122 xenial/linux-azure-edge: bug 1846121 xenial/linux-azure/azure-kernel: bug 1846120 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846123 Title: xenial/linux-azure: 4.15.0-1061.66 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846910] [NEW] nvidia-384 384.130-0ubuntu0.16.04.2: nvidia-384 kernel module failed to build
Public bug reported: upgrade reported an error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-384 384.130-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 DKMSKernelVersion: 4.4.0-165-generic Date: Sat Oct 5 15:51:17 2019 InstallationDate: Installed on 2016-09-05 (1125 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageVersion: 384.130-0ubuntu0.16.04.2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: nvidia-graphics-drivers-384 Title: nvidia-384 384.130-0ubuntu0.16.04.2: nvidia-384 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-384 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846910 Title: nvidia-384 384.130-0ubuntu0.16.04.2: nvidia-384 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1846910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846909] [NEW] Unresponsive While Navigating to ISO File
Public bug reported: I like the idea of using KVM virtual machines instead of Virtual Box, so I've been playing with Gnome-Boxes. Today, while trying to navigate to an ISO in GNOME-Boxes, the UI became very slow and ultimately unresponsive. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-boxes 3.32.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 5 17:39:19 2019 InstallationDate: Installed on 2019-10-03 (2 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-boxes UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-boxes (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages ** Attachment added: "boxes.png" https://bugs.launchpad.net/bugs/1846909/+attachment/5294645/+files/boxes.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846909 Title: Unresponsive While Navigating to ISO File To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-boxes/+bug/1846909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846907] Re: installing chrome-gnome-shell prevents tab and url bar context menus from working
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1846907 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. There was no package details, nor release information provided in your bug report. On providing this information, please change Status back to "New", or if you believe I'm in error, leave a comment stating why and it can be returned to "New". ** Changed in: chrome-gnome-shell (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/1846907 Title: installing chrome-gnome-shell prevents tab and url bar context menus from working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrome-gnome-shell/+bug/1846907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827822] Re: kernel null pointer dereference
I just had this happen to me. I'll attach the relevant part of the syslog. If there's any more info that I could give that would help just let me know. Using Kernel 5.3.0-10-generic from Eoan. Oct 5 18:02:26 kernel: [493310.092229] BUG: kernel NULL pointer dereference, address: 02ac Oct 5 18:02:26 kernel: [493310.092235] #PF: supervisor read access in kernel mode Oct 5 18:02:26 kernel: [493310.092237] #PF: error_code(0x) - not-present page Oct 5 18:02:26 kernel: [493310.092239] PGD 0 P4D 0 Oct 5 18:02:26 kernel: [493310.092244] Oops: [#1] SMP NOPTI Oct 5 18:02:26 kernel: [493310.092248] CPU: 0 PID: 2063 Comm: kworker/u32:3 Not tainted 5.3.0-10-generic #11-Ubuntu Oct 5 18:02:26 kernel: [493310.092250] Hardware name: Micro-Star International Co., Ltd MS-7C02/B450 TOMAHAWK (MS-7C02), BIOS 1.50 01/25/2019 Oct 5 18:02:26 kernel: [493310.092266] Workqueue: events_unbound commit_work [drm_kms_helper] Oct 5 18:02:26 kernel: [493310.092409] RIP: 0010:dc_stream_log+0x12/0xc0 [amdgpu] Oct 5 18:02:26 kernel: [493310.092414] Code: 83 f1 01 0f b6 c9 e8 8d 92 35 d3 e9 71 ff ff ff 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 f2 bf 04 00 00 00 48 89 e5 53 <8b> 86 ac 02 00 00 48 89 f3 8b 8e 0c 01 00 00 50 8b 86 28 01 00 00 Oct 5 18:02:26 kernel: [493310.092418] RSP: 0018:b81e08617b80 EFLAGS: 00010202 Oct 5 18:02:26 kernel: [493310.092422] RAX: RBX: 0001 RCX: 0002 Oct 5 18:02:26 kernel: [493310.092424] RDX: RSI: RDI: 0004 Oct 5 18:02:26 kernel: [493310.092427] RBP: b81e08617b88 R08: R09: 0001 Oct 5 18:02:26 kernel: [493310.092430] R10: 9c49fea173c8 R11: R12: 9c43047a Oct 5 18:02:26 kernel: [493310.092432] R13: 9c49f2e0 R14: 9c43047a R15: 9c49e90c Oct 5 18:02:26 kernel: [493310.092436] FS: () GS:9c49fea0() knlGS: Oct 5 18:02:26 kernel: [493310.092439] CS: 0010 DS: ES: CR0: 80050033 Oct 5 18:02:26 kernel: [493310.092441] CR2: 02ac CR3: 0007ecba CR4: 003406f0 Oct 5 18:02:26 kernel: [493310.092445] DR0: 1004c7c0 DR1: 10183c60 DR2: 100f14a0 Oct 5 18:02:26 kernel: [493310.092447] DR3: 100efd10 DR6: 0ff0 DR7: 0600 Oct 5 18:02:26 kernel: [493310.092449] Call Trace: Oct 5 18:02:26 kernel: [493310.092611] dc_commit_state+0x7e/0xb0 [amdgpu] Oct 5 18:02:26 kernel: [493310.092745] amdgpu_dm_atomic_commit_tail+0x3bf/0xfb0 [amdgpu] Oct 5 18:02:26 kernel: [493310.092753] ? cpumask_next_and+0x1e/0x20 Oct 5 18:02:26 kernel: [493310.092759] ? free_one_page+0xb7/0x4b0 Oct 5 18:02:26 kernel: [493310.092764] ? __switch_to_asm+0x40/0x70 Oct 5 18:02:26 kernel: [493310.092767] ? __switch_to_asm+0x34/0x70 Oct 5 18:02:26 kernel: [493310.092770] ? __switch_to_asm+0x40/0x70 Oct 5 18:02:26 kernel: [493310.092773] ? __switch_to_asm+0x34/0x70 Oct 5 18:02:26 kernel: [493310.092776] ? __switch_to_asm+0x40/0x70 Oct 5 18:02:26 kernel: [493310.092779] ? __switch_to_asm+0x34/0x70 Oct 5 18:02:26 kernel: [493310.092782] ? __switch_to_asm+0x40/0x70 Oct 5 18:02:26 kernel: [493310.092785] ? __switch_to_asm+0x34/0x70 Oct 5 18:02:26 kernel: [493310.092788] ? __switch_to_asm+0x40/0x70 Oct 5 18:02:26 kernel: [493310.092791] ? __switch_to_asm+0x34/0x70 Oct 5 18:02:26 kernel: [493310.092794] ? __switch_to_asm+0x40/0x70 Oct 5 18:02:26 kernel: [493310.092797] ? __switch_to_asm+0x34/0x70 Oct 5 18:02:26 kernel: [493310.092801] ? select_idle_sibling+0x1f/0x70 Oct 5 18:02:26 kernel: [493310.092804] ? select_task_rq_fair+0x379/0x5c0 Oct 5 18:02:26 kernel: [493310.092807] ? _cond_resched+0x19/0x30 Oct 5 18:02:26 kernel: [493310.092810] ? wait_for_completion_timeout+0x3a/0x120 Oct 5 18:02:26 kernel: [493310.092824] commit_tail+0x41/0x70 [drm_kms_helper] Oct 5 18:02:26 kernel: [493310.092836] ? commit_tail+0x41/0x70 [drm_kms_helper] Oct 5 18:02:26 kernel: [493310.092848] commit_work+0x12/0x20 [drm_kms_helper] Oct 5 18:02:26 kernel: [493310.092852] process_one_work+0x1db/0x380 Oct 5 18:02:26 kernel: [493310.092855] worker_thread+0x4d/0x400 Oct 5 18:02:26 kernel: [493310.092860] kthread+0x104/0x140 Oct 5 18:02:26 kernel: [493310.092863] ? process_one_work+0x380/0x380 Oct 5 18:02:26 kernel: [493310.092866] ? kthread_park+0x80/0x80 Oct 5 18:02:26 kernel: [493310.092870] ret_from_fork+0x22/0x40 Oct 5 18:02:26 kernel: [493310.092873] Modules linked in: ppp_mppe ppp_async nf_conntrack_pptp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c snd_seq_dummy ccm binfmt_misc edac_mce_amd kvm_amd snd_hda_codec_realtek snd_hda_codec_generic kvm ledtrig_audio irqbypass snd_hda_codec_hdmi snd_hda_intel snd_usb_audio snd_hda_codec snd_usbmidi_lib snd_hda_core mc snd_hwdep snd_pcm ath9k_htc
[Bug 1846842] Re: the upgrade tool from 19.04 to 19.10 failed badly
are you saying these 3 party packages caused the problem, because I am running gnome-shell (i.e not kde) does gnome-shell depend on kde ??, also shouldn't it have either worked around these problems or refused to upgrade??? in the past it coped with such stuff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846842 Title: the upgrade tool from 19.04 to 19.10 failed badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1846842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846908] [NEW] git-cola hijacks inode/directory
Public bug reported: After git-cola is installed, it hijacks inode/directory, so that (for example) when I click "Show in Folder" on a file download in Chrome, or plug in my phone, git-cola opens instead. I had to use "mimeopen -d" to fix this. ** Affects: git-cola (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/1846908 Title: git-cola hijacks inode/directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/git-cola/+bug/1846908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846130] Re: xenial/linux-hwe: 4.15.0-66.75~16.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1846131 packages: main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe phase: Testing phase-changed: Thursday, 03. October 2019 22:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-deeplens: bug 1846128 xenial/linux-hwe-edge: bug 1846127 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846130 Title: xenial/linux-hwe: 4.15.0-66.75~16.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846907] Re: installing chrome-gnome-shell prevents tab and url bar context menus from working
After removing the package and re-starting the browser, it works fine, demonstrates that removing the package resolves the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846907 Title: installing chrome-gnome-shell prevents tab and url bar context menus from working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrome-gnome-shell/+bug/1846907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846907] [NEW] installing chrome-gnome-shell prevents tab and url bar context menus from working
Public bug reported: In both google-chrome and chromium browsers, the context menu on tabs (that normally appears when right-clicking on a tab, allowing duplicating the tab, etc) and on the url bar (allowing copy and paste, etc), no longer appear. ** Affects: chrome-gnome-shell (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/1846907 Title: installing chrome-gnome-shell prevents tab and url bar context menus from working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrome-gnome-shell/+bug/1846907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846103] Re: bionic/linux-raspi2: 4.15.0-1049.53 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1846131 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Signoff phase-changed: Friday, 04. October 2019 01:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1846101 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846103 Title: bionic/linux-raspi2: 4.15.0-1049.53 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 788514] Re: python packages on the CDs not using dh_python2
** Changed in: bittornado (Debian) 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/788514 Title: python packages on the CDs not using dh_python2 To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/788514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846641] Re: eoan/linux: 5.3.0-17.18 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Saturday, 05. October 2019 01:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1846636 eoan/linux-aws: bug 1846613 eoan/linux-azure: bug 1846616 eoan/linux-gcp: bug 1846623 eoan/linux-kvm: bug 1846628 eoan/linux-oracle: bug 1846630 eoan/linux-raspi2: bug 1846611 eoan/linux-snapdragon: bug 1846634 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846641 Title: eoan/linux: 5.3.0-17.18 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846905] [NEW] package shim-signed 1.39+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1
Public bug reported: Ubuntu update reported this problem ProblemType: Package DistroRelease: Ubuntu 19.10 Package: shim-signed 1.39+15+1533136590.3beb971-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or directory: '/proc/sys/kernel/moksbstate_disabled' ApportVersion: 2.20.11-0ubuntu7 AptOrdering: shim:amd64: Install shim-signed:amd64: Install NULL: ConfigurePending Architecture: amd64 BootEFIContents: BOOTX64.CSV grub.cfg grubx64.efi mmx64.efi shimx64.efi Date: Sat Oct 5 21:13:42 2019 EFITables: paź 05 21:27:57 Nelken kernel: efi: EFI v2.40 by Lenovo paź 05 21:27:57 Nelken kernel: efi: SMBIOS=0x56fd4000 ACPI=0x57ffd000 ACPI 2.0=0x57ffd014 ESRT=0x56e4c000 TPMEventLog=0x49ce2018 paź 05 21:27:57 Nelken kernel: secureboot: Secure boot enabled paź 05 21:27:57 Nelken kernel: esrt: Reserving ESRT space from 0x56e4c000 to 0x56e4c088. ErrorMessage: installed shim-signed package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-10-05 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191001.2) Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.3-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SecureBoot: 6 0 0 0 1 SourcePackage: shim-signed Title: package shim-signed 1.39+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846905 Title: package shim-signed 1.39+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1846905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842954] Re: AMD GPU hang/crash/black screen after suspend(ing)
This has been fixed in: xserver-xorg-video-amdgpu 19.0.1-1ubuntu1 ** Changed in: xserver-xorg-video-amdgpu (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/1842954 Title: AMD GPU hang/crash/black screen after suspend(ing) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1842954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846899] Re: X won't start at boot with either nvidia driver
If it helps interpreting the logs: when the log file snapshot was taken, I was of course running the Nouveau drivers, 'cause that's the only way the system works. But the boot attempt immediately preceeding that was with the NVidia 390 drivers installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846899 Title: X won't start at boot with either nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1846899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846853] Re: Mouse scroll should control VOLUME NOT TIME
I WANT THE MOUSE SCROLL TO CONTROL VOLUME WHEREVER IT IS ON THE SCREEN. NEVER ANYTHING ELSE. THIS IS A MAJOR MAJOR BUG. FIX IT!!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846853 Title: Mouse scroll should control VOLUME NOT TIME To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1846853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846016] Re: iwlwifi regular scan timed out error sending statistics_cmd queue 0 is inactive
In one of the latest boots i've found red lines with some gdm3 error, so i gave gnome-shell a purge and reinstall and it worked. With the backport of iwlwifi i didn't have internet, but i uninstalled it and then was able to reinstall 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/1846016 Title: iwlwifi regular scan timed out error sending statistics_cmd queue 0 is inactive To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1846016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846900] [NEW] error install grub amd rysen 3 acer a315-41 notebook
Public bug reported: cannot install ubuntu on my new acer acpire a315-41-r9v0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 Date: Sat Oct 5 20:44:40 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash nomodeset --- LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846900 Title: error install grub amd rysen 3 acer a315-41 notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1846900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846899] [NEW] X won't start at boot with either nvidia driver
Public bug reported: The video card is a GeForce GT 730, which worked well with Ubuntu 16.04. After changing to Xubuntu 18.04, I can only run the Nouveau driver and the lack of acceleration is quite noticeable. When I try to enable the "tested" NVidia driver (390), the system never presents a log-in prompt, I just get a colorful display of large blinking gibberish. I have to go to the boot options, go directly to root prompt, and remove the NVidia driver. This make the system usable again, but I'm back to the Nouveau driver. I get similar symptoms with version 340.107 of the NVidia driver. It's a little hard to collect debug information when I can't get to a prompt to look at log files... Suggestions are welcome. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompositorRunning: None Date: Sat Oct 5 13:56:41 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 730] [10de:0f02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GF108 [GeForce GT 730] [19da:8199] InstallationDate: Installed on 2019-04-13 (175 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=d19b5e72-689e-4877-93dd-0d4bf5f7cc98 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4024 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4024:bd09/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Oct 5 13:56:03 2019 ** 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/1846899 Title: X won't start at boot with either nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1846899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846892] [NEW] Ubuntu 18.04.3 LTS freeze have to restart
Public bug reported: Sometime Ubuntu freezes and I have to do a hard shut down. At the moment I use Steam + protondb version 3.16-9 to play Dark Messiah of Might and Magic. I included the most important log 18:45:18 pulseaudio: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. 18:44:54 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 18:44:54 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 18:44:29 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 18:44:27 gnome-session-b: Unrecoverable failure in required component org.gnome.Shell.desktop 18:44:26 kernel: Couldn't get size: 0x800e I also included som other logs 18:59:27 systemd: Started Cleanup of Temporary Directories. 18:58:11 bash: Installing breakpad exception handler for appid(steam)/version(1569883362) 18:57:45 gdm-x-session: (II) modeset(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e) 18:57:45 bash: Failed to init SteamVR because it isn't installed 18:57:45 bash: Failed to init SteamVR because it isn't installed 18:57:45 bash: Installing breakpad exception handler for appid(steam)/version(1569883362) 18:57:45 bash: [1005/185745.060265:ERROR:buffer_manager.cc(488)] [.BrowserCompositor-0x16a562c76e00]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command 18:57:45 bash: [1005/185745.057516:INFO:crash_reporting.cc(268)] Crash reporting enabled for process: renderer 18:57:45 bash: [1005/185745.036102:ERROR:buffer_manager.cc(488)] [.BrowserCompositor-0x16a562a55300]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command 18:57:45 bash: [1005/185745.033075:INFO:crash_reporting.cc(268)] Crash reporting enabled for process: renderer 18:57:45 bash: [1005/185745.012080:ERROR:buffer_manager.cc(488)] [.BrowserCompositor-0x16a562bd8000]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command 18:57:45 bash: [1005/185745.002614:INFO:crash_reporting.cc(268)] Crash reporting enabled for process: renderer 18:57:44 bash: BRefreshApplicationsInLibrary 1: 3ms 18:57:44 bash: migrating temporary roaming config store 18:57:44 bash: roaming config store loaded successfully - 1269 bytes. 18:57:43 bash: ERROR_EXTENSION_NOT_PRESENT 18:57:43 bash: Could not create Vulkan instance : 18:57:43 bash: Installing breakpad exception handler for appid(steam)/version(1569883362) 18:57:43 gnome-shell: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.84/org/ayatana/NotificationItem/steam 18:57:42 bash: (steam:3161): Gtk-WARNING **: gtk_disable_setlocale() must be called before gtk_init() 18:57:42 gdm-x-session: (II) modeset(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e) 18:57:42 bash: Gtk-Message: Failed to load module "atk-bridge" 18:53:03 rtkit-daemon: Supervising 22 threads of 10 processes of 1 users. 18:50:59 nautilus: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory) 18:50:59 systemd: Started Virtual filesystem metadata service. 18:50:59 dbus-daemon: [session uid=1000 pid=1652] Successfully activated service 'org.gtk.vfs.Metadata' 18:50:59 systemd: Starting Virtual filesystem metadata service... 18:50:59 dbus-daemon: [session uid=1000 pid=1652] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.76' (uid=1000 pid=2863 comm="/usr/bin/nautilus --gapplication-service " label="unconfined") 18:50:56 kernel: audit: type=1400 audit(1570294256.326:72): apparmor="DENIED" operation="open" profile="snap.gnome-logs.gnome-logs" name="/proc/2359/mounts" pid=2359 comm="gnome-logs" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 18:50:56 kernel: kauditd_printk_skb: 10 callbacks suppressed 18:50:56 gnome-logs: AVC apparmor="DENIED" operation="open" profile="snap.gnome-logs.gnome-logs" name="/proc/2359/mounts" pid=2359 comm="gnome-logs" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 18:50:45 kernel: USER_AVC pid=836 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/hostname1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.150" pid=2359 label="snap.gnome-logs.gnome-logs" peer_pid=2856 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' 18:50:45 systemd: Started Hostname Service. 18:50:45 dbus-daemon: [system] Successfully activated service 'org.freedesktop.hostname1' 18:50:45 pool: AVC apparmor="DENIED"
[Bug 1846891] [NEW] With all plugins enabled Pluma shows "gi.repository.GLib.Error: gtk-source-completion-error-quark: Provider is not bound to this completion object (1)" in terminal on close
Public bug reported: Steps to reproduce: 1. Install Ubuntu MATE 19.04 2. Launch Pluma and enable all Plugins 3. Close Pluma 4. Launch terminal and issue `pluma` command 5. Close Pluma window Expected results: * Pluma closed without messages in the terminal Actual results: * Pluma closed with the following errors in the terminal: Traceback (most recent call last): File "/usr/lib/x86_64-linux-gnu/pluma/plugins/snippets/Document.py", line 702, in on_view_destroy self.stop() File "/usr/lib/x86_64-linux-gnu/pluma/plugins/snippets/Document.py", line 70, in stop self.set_view(None) File "/usr/lib/x86_64-linux-gnu/pluma/plugins/snippets/Document.py", line 149, in set_view self._set_view(view) File "/usr/lib/x86_64-linux-gnu/pluma/plugins/snippets/Document.py", line 113, in _set_view completion.remove_provider(self.provider) gi.repository.GLib.Error: gtk-source-completion-error-quark: Provider is not bound to this completion object (1) Note: the 19.10 is also affected. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pluma 1.20.4-1 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: MATE Date: Sat Oct 5 19:45:10 2019 InstallationDate: Installed on 2019-04-18 (169 days ago) InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pluma UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pluma (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846891 Title: With all plugins enabled Pluma shows "gi.repository.GLib.Error: gtk- source-completion-error-quark: Provider is not bound to this completion object (1)" in terminal on close To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pluma/+bug/1846891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743134] Re: "TypeError: Couldn't find foreign struct converter for 'cairo.Context'" after enabling all plugins in Pluma
Still happens on 19.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743134 Title: "TypeError: Couldn't find foreign struct converter for 'cairo.Context'" after enabling all plugins in Pluma To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pluma/+bug/1743134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846890] Re: Unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpythonloader.so
Quick and dirty has is to create a symlink between new file name `libpython2loader.so` (see https://packages.ubuntu.com/eoan/amd64/libpeas-1.0-python2loader/filelist ) and expected old one (see https://packages.ubuntu.com/disco/amd64/libpeas-1.0-python2loader/filelist ): ``` sudo ln -s /usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpython2loader.so /usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpythonloader.so ``` ** Summary changed: - Unable to enable plugins 9External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpythonloader.so + Unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpythonloader.so ** Description changed: Steps to reproduce: 1. Install Ubuntu 19.10 2. Launch Pluma 3. Go to Edit -> Preferences, switch to Plugins tab 4. Try enable all plugins by checking their checkmarks Expected results: * all plugins are enabled without errors or warnings; Actual results: * plugin(s) are not enabled, show the following errors in `pluma`'s terminal: ``` - $ pluma + $ pluma (pluma:1685): libpeas-WARNING **: 19:20:59.204: Failed to load module 'pythonloader': /usr/lib/x86_64-linux- gnu/libpeas-1.0/loaders/libpythonloader.so: cannot open shared object file: No such file or directory (pluma:1685): libpeas-WARNING **: 19:20:59.205: Could not load plugin loader 'python' ``` Note: in previous releases the `libpythonloader.so` was located in libpeas-1.0-python2loader package (see https://packages.ubuntu.com/search?suite=disco=amd64=exactfilename=contents=libpythonloader.so - ) but it is missed in 19.10 repository. + ) but this file is missed in 19.10 repository. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pluma 1.22.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Sat Oct 5 19:23:02 2019 InstallationDate: Installed on 2019-10-05 (0 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191004) SourcePackage: pluma UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846890 Title: Unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux- gnu/libpeas-1.0/loaders/libpythonloader.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pluma/+bug/1846890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846890] [NEW] Unable to enable plugins 9External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpythonloader.so
Public bug reported: Steps to reproduce: 1. Install Ubuntu 19.10 2. Launch Pluma 3. Go to Edit -> Preferences, switch to Plugins tab 4. Try enable all plugins by checking their checkmarks Expected results: * all plugins are enabled without errors or warnings; Actual results: * plugin(s) are not enabled, show the following errors in `pluma`'s terminal: ``` $ pluma (pluma:1685): libpeas-WARNING **: 19:20:59.204: Failed to load module 'pythonloader': /usr/lib/x86_64-linux- gnu/libpeas-1.0/loaders/libpythonloader.so: cannot open shared object file: No such file or directory (pluma:1685): libpeas-WARNING **: 19:20:59.205: Could not load plugin loader 'python' ``` Note: in previous releases the `libpythonloader.so` was located in libpeas-1.0-python2loader package (see https://packages.ubuntu.com/search?suite=disco=amd64=exactfilename=contents=libpythonloader.so ) but it is missed in 19.10 repository. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pluma 1.22.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Sat Oct 5 19:23:02 2019 InstallationDate: Installed on 2019-10-05 (0 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191004) SourcePackage: pluma UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pluma (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "stop signs in the Pluma Plugins setup window" https://bugs.launchpad.net/bugs/1846890/+attachment/5294569/+files/pluma-plugins-errors.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846890 Title: Unable to enable plugins 9External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux- gnu/libpeas-1.0/loaders/libpythonloader.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pluma/+bug/1846890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg
Jeremy Soller's fix to edit Xwrapper seems to be good. The edits to the gdm service cause a crash to happen on boot. Currently using an HP Laptop with an Intel CPU and Nvidia GPU that I believe is Optimus. I have the proprietary Nvidia driver running on nvidia-driver-430 as of this comment's date. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846445] Re: 19.10 gnome tweaks flashing and unusable
This bug is easy to duplicate. Here are the steps: 1. Install Ubuntu 19.10 with a fresh install. 2. Install all the updates. 3. Install the gnome-tweaks tool. 4. Open the gnome-tweaks too. It may not occur immediately, however, once you get down to the "Window Titlebars" section, change the Titlebar buttons or Placement options and at the point the tool will never work again and will be liked originally described. The up-and-down arrows will allow you to change sections. You just have to make sure you move your left arrow first to ensure you are all the way on the left side before moving up/down. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846445 Title: 19.10 gnome tweaks flashing and unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zulucrypt/+bug/1846445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846445] Re: 19.10 gnome tweaks flashing and unusable
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zulucrypt (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/1846445 Title: 19.10 gnome tweaks flashing and unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zulucrypt/+bug/1846445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516852] Re: wireless connection drops despite full signal
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (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/1516852 Title: wireless connection drops despite full signal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1516852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846871] Re: Desktop Icons NG shell extension breaks Activities vew
Extensions are released for everyone, not specifically for Ubuntu, so not the extension developer's responsibility to check, which distros would work. Quote https://extensions.gnome.org/about/ "All extensions uploaded to this site are carefully reviewed for malicious behavior before they are made available for download." As users are normal people, they'd try out any extension out there, and Ubuntu 19.10 would fail. Any extension downloaded from https://extensions.gnome.org/about/ would install it in ~/.local/share/gnome-shell/extensions and would override the system extension, user comes first. Both extensions are from the same author, whatever the name of the extension (for example, desktop-icons@csoriano). If we take the system Desktop Icons extension, it cannot be blocked from any future development by the author/maintainer. What we call Desktop Icons system extension is static, as it is, while the maintainer had upgraded it few days ago. The bug is here in Ubuntu Eoan, not with the extension. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846871 Title: Desktop Icons NG shell extension breaks Activities vew To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845031] Re: gnome not remembering numlock state in eoan
Prior to filing a bug myself I searched launchpad for "num lock", so this bug with "numlock" in the title did not show up. The bug I filed is Bug #1846249. I am experiencing the same issue under 19.10 when logged in with Wayland. The problem is not present in an X session. In fact I can do the following: (1) boot the computer with the numlock key (led) active (2) login to a Wayland session and the number keys won't work but num key led is on (3) log out (not reboot) and log into an X session (4) number keys work immediately (have not touched numlock key and led is still on) (5) log out (not reboot) and lot back into a Wayland session (6) number keys do not work unless I hit numlock key which turns off the numlock led The relevant gsettings for numlock can be found in my bug report as well as some other logs and information: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/1846249 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845031 Title: gnome not remembering numlock state in eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1845031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846249] Re: Num lock works in reverse on Ubuntu 19.10 wayland
** Package changed: x11-utils (Ubuntu) => gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846249 Title: Num lock works in reverse on Ubuntu 19.10 wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1846249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846064] Re: xenial/linux-snapdragon: 4.4.0-1128.136 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1846069 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Signoff phase-changed: Thursday, 03. October 2019 18:27 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1846063 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846064 Title: xenial/linux-snapdragon: 4.4.0-1128.136 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846888] [NEW] pdfposter hangs in 18.04
Public bug reported:
Just installed version 0.6.0 from the repository for 18.04 and when creating a
poster the program just hangs, no msg, no output.
After a ctrl-c the following occured:
pdfposter --scale=4 Micro-Magic_Plan_2016_V2.pdf Plan.pdf
^CTraceback (most recent call last):
File "/usr/bin/pdfposter", line 9, in
load_entry_point('pdftools.pdfposter==0.6.0', 'console_scripts',
'pdfposter')()
File "/usr/share/pdfposter/pdftools/pdfposter/cmd.py", line 129, in run
main(opts, *args)
File "/usr/share/pdfposter/pdftools/pdfposter/__init__.py", line 340, in main
outpdf.write(open(outfilename, 'wb'))
File "/usr/lib/python2.7/dist-packages/PyPDF2/pdf.py", line 501, in write
obj.writeToStream(stream, key)
File "/usr/lib/python2.7/dist-packages/PyPDF2/generic.py", line 785, in
writeToStream
self[NameObject("/Length")] = NumberObject(len(self._data))
File "/usr/lib/python2.7/dist-packages/PyPDF2/pdf.py", line 2769, in _getData
op.writeToStream(newdata, None)
File "/usr/lib/python2.7/dist-packages/PyPDF2/generic.py", line 252, in
writeToStream
stream.write(b_(repr(self)))
File "/usr/lib/python2.7/dist-packages/PyPDF2/generic.py", line 242, in
__repr__
o = "%.5f" % self
TypeError: float argument required, not FloatObject
I have the latest versions of python2 installed, and PyPDF2 is
installed.
** Affects: pdfposter (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/1846888
Title:
pdfposter hangs in 18.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pdfposter/+bug/1846888/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845031] Re: gnome not remembering numlock state in eoan
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (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/1845031 Title: gnome not remembering numlock state in eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1845031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846062] Re: xenial/linux-raspi2: 4.4.0-1124.133 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1846069 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Signoff phase-changed: Thursday, 03. October 2019 18:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1846061 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846062 Title: xenial/linux-raspi2: 4.4.0-1124.133 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846853] Re: Mouse scroll should control VOLUME NOT TIME
** Tags added: bionic disco eoan xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846853 Title: Mouse scroll should control VOLUME NOT TIME To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1846853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846069] Re: xenial/linux: 4.4.0-166.195 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 03. October 2019 14:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1846066 trusty/linux-lts-xenial: bug 1846067 xenial/linux-aws: bug 1846059 xenial/linux-fips: bug 1846065 xenial/linux-kvm: bug 1846060 xenial/linux-raspi2: bug 1846062 xenial/linux-snapdragon: bug 1846064 xenial/linux/caracalla-kernel: bug 1846054 xenial/linux/pc-kernel: bug 1846055 xenial/linux/stlouis-kernel: bug 1846057 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846069 Title: xenial/linux: 4.4.0-166.195 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846059] Re: xenial/linux-aws: 4.4.0-1096.107 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1846069 packages: main: linux-aws meta: linux-meta-aws phase: Signoff phase-changed: Thursday, 03. October 2019 19:50 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-aws/aws-kernel: bug 1846058 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846059 Title: xenial/linux-aws: 4.4.0-1096.107 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846853] Re: Mouse scroll should control VOLUME NOT TIME
** Changed in: totem Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846853 Title: Mouse scroll should control VOLUME NOT TIME To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1846853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846853] Re: Mouse scroll should control VOLUME NOT TIME
To control the volume by scrolling the mouse wheel you need to hold the mouse pointer over the volume icon. A change in this functionality was requested over 10 years ago directly to the GNOME developers, the authors of the Totem application. The upstream bug report shows that this request is still outstanding. https://gitlab.gnome.org/GNOME/totem/issues/20 ** Bug watch added: gitlab.gnome.org/GNOME/totem/issues #20 https://gitlab.gnome.org/GNOME/totem/issues/20 ** Also affects: totem via https://gitlab.gnome.org/GNOME/totem/issues/20 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846853 Title: Mouse scroll should control VOLUME NOT TIME To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1846853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822736] Re: Passwords longer than 255 characters break authentication
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Public Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822736 Title: Passwords longer than 255 characters break authentication To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1822736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773653] Re: Window decoration small, blurry on HiDPI
Working on it: * https://twitter.com/m_wimpress/status/1180493276383780866 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773653 Title: Window decoration small, blurry on HiDPI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1773653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846871] Re: Desktop Icons NG shell extension breaks Activities vew
Maybe there's a way to workaround it on the Ubuntu side, but I think the greater responsibility is on the NG developer side. Please file a bug with NG instead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846871 Title: Desktop Icons NG shell extension breaks Activities vew To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846871] Re: Desktop Icons NG shell extension breaks Activities vew
It seems to work fine on Ubuntu using GNOME vanilla session. I don't know if it has been reported already to Carlos (I didn't know he was the maintainer), but I wonder if it's possible to fix the status of Desktop Icon on Ubuntu, since it doesn't seem to be possible to disable it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846871 Title: Desktop Icons NG shell extension breaks Activities vew To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846871] Re: Desktop Icons NG shell extension breaks Activities vew
You can find the Ubuntu Desktop Icons System Extension here; https://gitlab.gnome.org/World/ShellExtensions/desktop-icons and here; https://extensions.gnome.org/extension/1465/desktop-icons/ Both links install the same desktop-icons@csoriano The NG extension allows drag and drop, but won't work in Ubuntu, default session or vanilla session. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846871 Title: Desktop Icons NG shell extension breaks Activities vew To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846871] Re: Desktop Icons NG shell extension breaks Activities vew
On GNOME vanilla session, enabling both extensions it shows a different behavior. Everything seems to work properly except that GNOME-Tweaks fails to start (Failed to register: Timeout was reached) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846871 Title: Desktop Icons NG shell extension breaks Activities vew To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846842] Re: the upgrade tool from 19.04 to 19.10 failed badly
>From VarLogDistupgradeAptlog.txt Investigating (0) kde-style-breeze-qt4:amd64 < 4:5.15.4.1-0ubuntu1 @ii mK Ib > Broken kde-style-breeze-qt4:amd64 Depends on kde-style-breeze:amd64 < 4:5.15.4.1-0ubuntu1 -> 4:5.16.5-0ubuntu1 @ii umU > (= 4:5.15.4.1-0ubuntu1) Qt4 is OLD/depreciated & likely expected on upgrade (https://packages.ubuntu.com/search?suite=all=names =kde-style-breeze-qt4) https://packages.ubuntu.com/disco/kde-style-breeze-qt4 shows "kde- style-breeze (= 4:5.15.4.1-0ubuntu1)" which is a problem I suspect so leaving it.. I suspect this MAY impact other users upgrading from 19.04 to 19.10 -- Other issues that may be 3rd party related Investigating (0) libomp-9-dev:amd64 < none -> 1:9-1 @un uN Ib > Broken libomp-9-dev:amd64 Conflicts on libomp-x.y-dev:amd64 < none @un H > Looks like 3rd party packages; possibly a reason to reject, "ERROR:root:Package seamonkey-mozilla-build has no priority set ERROR:root:not handled exception:" is likely 3rd party/PPA & reject.. but ignoring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846842 Title: the upgrade tool from 19.04 to 19.10 failed badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1846842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846871] Re: Desktop Icons NG shell extension breaks Activities vew
It affects both Ubuntu session and vanilla Gnome session. In Arch Linux, there's only a vanilla Gnome session, and it works there. This NG extension is been there for few months. The NG developer is the same person that maintains the UBuntu Desktop Icons system extension. His extension is named desktop-icons@csoriano, so probably cannot become.stay as a system extension. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846871 Title: Desktop Icons NG shell extension breaks Activities vew To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785143] Re: xfce4-settings-manager crashed with SIGSEGV in gtk_drag_finish()
This looks like a copy of the bug #1785143, but it appeared while trying to launch the program originally intended for ubuntu 14.04. The program is: "prime-indicator_0.1-1+git20150211~webupd8~1_all". The program itself works correctly, however, when trying to change the graphics card from Intel to nvidia, the above error appears. The error does not directly affect the Ubuntu package, but affects the functioning of the whole. Interestingly, the program allowed the graphics card to switch correctly, so it works correctly. Dell Inspiron7000 series, i7-7700HQ (intel HD graf. 630 and Nvidia GF1050TI), 32GB RAM. Xubuntu 19.10 dev. branch, ISO 04 okt. 2019, updates of 05 okt. 2019. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785143 Title: xfce4-settings-manager crashed with SIGSEGV in gtk_drag_finish() To manage notifications about this bug go to: https://bugs.launchpad.net/xfwm4/+bug/1785143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846842] Re: the upgrade tool from 19.04 to 19.10 failed badly
** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846842 Title: the upgrade tool from 19.04 to 19.10 failed badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1846842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846271] Re: Full video freeze kernel 4.15.0-65
It's not enabled on 16.04 but it's default enabled on 18.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846271 Title: Full video freeze kernel 4.15.0-65 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846271] Re: Full video freeze kernel 4.15.0-65
I am in the process of evaluating a replacement for Mint/Ubuntu. I have used many distros, but Mint/Ubuntu is the ONLY Linux distro to ever freeze-up and to require a restart (who do you think you are...MS?). It has happened on 2 different desktop PCs, the only similarity is AMD processors. If you need the journal for instances like this, then why isn't it enabled by default? Do what you want with what I have reported to you as I am done with this back and forth messaging getting absolutely nowhere. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846271 Title: Full video freeze kernel 4.15.0-65 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845703] Re: Deleting starred files leaves behind starred file named ""
** Changed in: nautilus Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845703 Title: Deleting starred files leaves behind starred file named "" To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1845703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846842] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1846842/+attachment/5294564/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846842 Title: the upgrade tool from 19.04 to 19.10 failed badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1846842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846842] Re: the upgrade tool from 19.04 to 19.10 failed badly
apport information ** Tags added: apport-collected dist-upgrade eoan ** Description changed: I upgraded my old crappy box to 19.10 beta from 19.04, things did not go well the upgrade tool eoan it did not run well I could not get many of the buttons to work by clicking I had to use tab and enter, then the thing that's supposed stop it locking fail while I was asleep; woke up it was locked, and when I tried to unlock it I just got a blank screen. - I had to ssh in to it find out what was going on I found it was stuck I - gave it an hour to come out of it, it didn't, so I killed the processes - with sudo kill -1 pid-of-the-python-program pid-of-the-shell-script then - I rebooted it by sudo shutdown, and ssh in again and it was still sick - and half done, so I called sudo apt upgrade, which didn't work but gave - me the dpkg (sudo dpkg --configure -a) command to use, I ran that and it - cleaned it up a lot, and I was able to login to gnome-shell it was still - on version 3.32.2 and was a little messed up but worked, I tried the - update-manager -d &, that gave me a partial upgrade program which - failed, in the end, I fixed it with sudo apt-get dist-upgrade and - running the normal update-manager program till every thing was up to - date, now it's fine but it took much drama to do it + I had to ssh in to it find out what was going on I found it was stuck I gave it an hour to come out of it, it didn't, so I killed the processes with sudo kill -1 pid-of-the-python-program pid-of-the-shell-script then I rebooted it by sudo shutdown, and ssh in again and it was still sick and half done, so I called sudo apt upgrade, which didn't work but gave me the dpkg (sudo dpkg --configure -a) command to use, I ran that and it cleaned it up a lot, and I was able to login to gnome-shell it was still on version 3.32.2 and was a little messed up but worked, I tried the update-manager -d &, that gave me a partial upgrade program which failed, in the end, I fixed it with sudo apt-get dist-upgrade and running the normal update-manager program till every thing was up to date, now it's fine but it took much drama to do it + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu7 + Architecture: amd64 + CrashDB: ubuntu + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.10 + InstallationDate: Installed on 2017-07-24 (803 days ago) + InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) + Package: ubuntu-release-upgrader (not installed) + ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 + Tags: eoan dist-upgrade + Uname: Linux 5.3.0-13-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin mail plugdev sambashare staff sudo + VarLogDistupgradeTermlog: + + _MarkForUpload: True ** Attachment added: "CurrentDmesg.txt.txt" https://bugs.launchpad.net/bugs/1846842/+attachment/5294562/+files/CurrentDmesg.txt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846842 Title: the upgrade tool from 19.04 to 19.10 failed badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1846842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846842] VarLogDistupgradeAptclonesystemstate.tar.gz
apport information ** Attachment added: "VarLogDistupgradeAptclonesystemstate.tar.gz" https://bugs.launchpad.net/bugs/1846842/+attachment/5294565/+files/VarLogDistupgradeAptclonesystemstate.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846842 Title: the upgrade tool from 19.04 to 19.10 failed badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1846842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846842] VarLogDistupgradeLspcitxt.txt
apport information ** Attachment added: "VarLogDistupgradeLspcitxt.txt" https://bugs.launchpad.net/bugs/1846842/+attachment/5294567/+files/VarLogDistupgradeLspcitxt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846842 Title: the upgrade tool from 19.04 to 19.10 failed badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1846842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846842] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1846842/+attachment/5294563/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846842 Title: the upgrade tool from 19.04 to 19.10 failed badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1846842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846842] VarLogDistupgradeAptlog.txt
apport information ** Attachment added: "VarLogDistupgradeAptlog.txt" https://bugs.launchpad.net/bugs/1846842/+attachment/5294566/+files/VarLogDistupgradeAptlog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846842 Title: the upgrade tool from 19.04 to 19.10 failed badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1846842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774640] Re: Bluetooth turns off automatically Ubuntu 18.04 LTS
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (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/1774640 Title: Bluetooth turns off automatically Ubuntu 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1774640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846871] Re: Desktop Icons NG shell extension breaks Activities vew
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (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/1846871 Title: Desktop Icons NG shell extension breaks Activities vew To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846503] Re: Installing just one extension makes Ubuntu Eoan to fail
*** This bug is a duplicate of bug 1846871 *** https://bugs.launchpad.net/bugs/1846871 ** This bug has been marked a duplicate of bug 1846871 Desktop Icons NG shell extension breaks Activities vew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846503 Title: Installing just one extension makes Ubuntu Eoan to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1846503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846871] Re: Desktop Icons NG shell extension breaks Activities vew
Does this bug affect the vanilla GNOME session or only the Ubuntu session? If it only affects the Ubuntu session, it is probably just a compatibility problem between Ubuntu's desktop icons extension and the "NG" extension. Since the "NG" extension is newer, I think it's appropriate for the "NG" extension to not break systems where the official desktop icons extension is already installed. Please report this issue to the NG developers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846871 Title: Desktop Icons NG shell extension breaks Activities vew To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841485] Re: Unbearable whistling in headphones
Thank you and good luck for trying to solve this very annoying bug. Regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841485 Title: Unbearable whistling in headphones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844781] Re: Thunar fails to scroll to the end of the file list
** Changed in: exo Status: Confirmed => 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/1844781 Title: Thunar fails to scroll to the end of the file list To manage notifications about this bug go to: https://bugs.launchpad.net/exo/+bug/1844781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
