[Bug 1968198] Re: Issue with mirroring 22.04 on a 20.04 host.
** Description changed: - On a 20.04 host with reprepro 5.3.0-1.3~ubuntu20.04 I'm trying to mirror 22.04 but get the following: + On a fully patched 20.04 as of the date of posting with reprepro + 5.3.0-1.3~ubuntu20.04 I'm trying to mirror 22.04. + With the same config I'm able to mirror xenial, bionic and focal. + This is supposed to have a fix released in: #1923845 and #1933363 but still getting the following issue: Got 100%: 97G 51M bytes Installing (and possibly deleting) packages... - zstd: error 70 : Write error : cannot write decoded block : Broken pipe - zstd: error 70 : Write error : cannot write decoded block : Broken pipe - zstd: error 70 : Write error : cannot write decoded block : Broken pipe - zstd: error 70 : Write error : cannot write decoded block : Broken pipe - zstd: error 70 : Write error : cannot write decoded block : Broken pipe - zstd: /*stdout*\: Broken pipe - zstd: error 70 : Write error : cannot write decoded block : Broken pipe zstd: error 70 : Write error : cannot write decoded block : Broken pipe + zstd: error 70 : Write error : cannot write decoded block : Broken pipe + zstd: error 70 : Write error : cannot write decoded block : Broken pipe + zstd: error 70 : Write error : cannot write decoded block : Broken pipe + zstd: error 70 : Write error : cannot write decoded block : Broken pipe + zstd: /*stdout*\: Broken pipe + zstd: error 70 : Write error : cannot write decoded block : Broken pipe + zstd: error 70 : Write error : cannot write decoded block : Broken pipe + + + + The config: + root@archive2:/opt/reprepro/conf/jammy# cat distributions + Origin: ubuntu + Suite: jammy + Codename: jammy + Architectures: amd64 + Components: main multiverse restricted universe + UDebComponents: main multiverse restricted universe + Description: jammy + DebIndices: Packages Release . .gz .bz2 + DscIndices: Sources Release .gz .bz2 + SignWith: Ourprivatekey + Update: jammy + + root@archive2:/opt/reprepro/conf/jammy# cat updates + Name: jammy + Method: http://archive.ubuntu.com/ubuntu + Suite: jammy + Architectures: amd64 + VerifyRelease: D94AA3F0EFE21092|40976EAF437D05B5|3B4FE6ACC0B21F32|871920D1991BC93C -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968198 Title: Issue with mirroring 22.04 on a 20.04 host. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/reprepro/+bug/1968198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968198] [NEW] Issue with mirroring 22.04 on a 20.04 host.
Public bug reported: On a 20.04 host with reprepro 5.3.0-1.3~ubuntu20.04 I'm trying to mirror 22.04 but get the following: With the same config I'm able to mirror xenial, bionic and focal. Got 100%: 97G 51M bytes Installing (and possibly deleting) packages... zstd: error 70 : Write error : cannot write decoded block : Broken pipe zstd: error 70 : Write error : cannot write decoded block : Broken pipe zstd: error 70 : Write error : cannot write decoded block : Broken pipe zstd: error 70 : Write error : cannot write decoded block : Broken pipe zstd: error 70 : Write error : cannot write decoded block : Broken pipe zstd: /*stdout*\: Broken pipe zstd: error 70 : Write error : cannot write decoded block : Broken pipe zstd: error 70 : Write error : cannot write decoded block : Broken pipe ** Affects: reprepro (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/1968198 Title: Issue with mirroring 22.04 on a 20.04 host. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/reprepro/+bug/1968198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947210]
I do not know how to add "Wayland" to the bug summary, nor do I know how to flag this for possible closing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947210 Title: Firefox Snap can't copy or drag in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1947210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947210]
I am not the bug reporter but I am finding that copy / paste & drag / drop in the Firefox snap is working under Wayland now. The current stable release of the snap of Firefox is 97.0; I don't know when it started working as I was using a .deb version of Firefox under xorg for other reasons. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947210 Title: Firefox Snap can't copy or drag in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1947210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947210] Re: Firefox Snap can't copy or drag in Wayland
@Sebastien Bacher (@seb128) I tried the procedure in Bug #1913775 and saw some strange behavior but I believe it must not be exactly the same issue. The bug I originally reported seems to be resolved in Firefox 97.0 snap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947210 Title: Firefox Snap can't copy or drag in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1947210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947210] Re: Firefox Snap can't copy or drag in Wayland
My apologies to everyone who responded since I reported it in October -- apparently I missed seeing the notifications for this bug. I also installed a deb version and have been logging in via xorg to avoid it, and another bug affecting Zoom under Wayland. I just installed the current stable snap version and logged in via Wayland and copy/paste and drag/drop seem to be working fine both ways. Should I mark the bug resolved or is that my responsibility? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947210 Title: Firefox Snap can't copy or drag in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1947210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] Re: Coroutines are racy for risc64 emu on arm64 - crash on Assertion
No, as I described in great detail it has nothing to do with the attached devices. I just noticed that the bug was excused away as being do to the “slow” RPi 4. I’ll share that I originally hit it on Apple’s M1 but as I expect my environment might be too unusual I replicated it on RPi 4. I have since switched to building qemu from source so I don’t know if it still happens. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Coroutines are racy for risc64 emu on arm64 - crash on Assertion To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1921664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957261] [NEW] PHP modules don't load
Public bug reported: I tried to install Ubuntu Server 22.04 with PHP 8.0 with some PHP modules. Most of them loaded just fine but I had problems making php- apcu and php-imagick to load. It is likely a version mismatch (8.1 vs 8.0) and uninstalling the package and installing from "pecl install" did the trick. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: php-apcu 5.1.20+4.0.11-0+deb11u1ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jan 12 18:34:24 2022 InstallationDate: Installed on 2022-01-11 (1 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220106) SourcePackage: php-apcu UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: php-apcu (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957261 Title: PHP modules don't load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-apcu/+bug/1957261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950996] Re: Missing all modules for usb nics in initrd which makes PXE boot impossible
** Description changed: - Initramfs taken from the live iso for PXE boot does not contain USB NIC + initrd taken from the live iso for PXE boot does not contain USB NIC drivers which makes PXE installation/netboot impossible via usb. + + This is the case on 20.04 server iso (both hwe and normal kernel/initrd) + and desktop iso. "kernel/drivers/net/usb" is empty and needs to be included in the initramfs build. As most modern thin laptops lack physical rj45 ethernet this is a big issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.8.0-64.72-generic 5.8.18 Uname: Linux 5.8.0-64-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 15 16:47:45 2021 PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: Upgraded to focal on 2020-05-11 (552 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950996 Title: Missing all modules for usb nics in initrd which makes PXE boot impossible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1950996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950996] [NEW] Missing all modules for usb nics in initrd which makes PXE boot impossible
Public bug reported: Initramfs taken from the live iso for PXE boot does not contain USB NIC drivers which makes PXE installation/netboot impossible via usb. "kernel/drivers/net/usb" is empty and needs to be included in the initramfs build. As most modern thin laptops lack physical rj45 ethernet this is a big issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.8.0-64.72-generic 5.8.18 Uname: Linux 5.8.0-64-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 15 16:47:45 2021 PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: Upgraded to focal on 2020-05-11 (552 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Assignee: Dimitri John Ledkov (xnox) Status: Triaged ** Affects: initramfs-tools (Ubuntu Focal) Importance: Undecided Status: New ** Affects: initramfs-tools (Ubuntu Hirsute) Importance: Undecided Status: New ** Affects: initramfs-tools (Ubuntu Impish) Importance: Undecided Status: New ** Affects: initramfs-tools (Ubuntu Jammy) Importance: Undecided Assignee: Dimitri John Ledkov (xnox) Status: Triaged ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950996 Title: Missing all modules for usb nics in initrd which makes PXE boot impossible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1950996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947210] Re: Firefox Snap can't copy or drag in Wayland
** Tags added: wayland -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947210 Title: Firefox Snap can't copy or drag in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1947210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947210] [NEW] Firefox Snap can't copy or drag in Wayland
Public bug reported: I just upgraded to 21.10 Impish which supplies Firefox 93.0-1 via snap. I could not copy and paste to and from the browser. I logged out of Wayland and into Xorg and copy & paste works. Already reported at https://bugzilla.mozilla.org/show_bug.cgi?id=1729901 so it's a known issue. I wanted to report it here so it gets into the Impish release notes or wherever along with the workaround. ** Affects: firefox Importance: Unknown Status: Unknown ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: snap ** Bug watch added: Mozilla Bugzilla #1729901 https://bugzilla.mozilla.org/show_bug.cgi?id=1729901 ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1729901 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/1947210 Title: Firefox Snap can't copy or drag in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1947210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904312] Re: cant see list of programs in ubuntu software center
Sounds like software-center NOT ubuntu-release-upgrader package ** Also affects: software-center (Ubuntu) Importance: Undecided Status: New ** No longer affects: software-center (Ubuntu) ** Package changed: ubuntu-release-upgrader (Ubuntu) => software-center (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904312 Title: cant see list of programs in ubuntu software center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1904312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931193] Re: typecatcher crashes on launch
I just fired up a VM of 21.04 Hirsute and typecatcher crashes with the same error on a new VM -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931193 Title: typecatcher crashes on launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/typecatcher/+bug/1931193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931193] Re: typecatcher crashes on launch
Working on the local cache theory I tried running typecatcher in another user account on this system but which did NOT have any user account installed fonts. It crashes in the same way as shown at top; font- manager runs fine, and confirms no locally-installed fonts in the other user's account. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931193 Title: typecatcher crashes on launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/typecatcher/+bug/1931193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931193] Re: typecatcher crashes on launch
I read that font-manager had the feature I needed at the moment so I used the Software Center to install it. For some reason the flatpak version it chose worked at first then crashed. So I uninstalled the flatpak and used apt to install the version in hirsute, which has worked just fine. I think it's possible I have some weird cruft in my local font caches or somewhere leftover from the upgrade from groovy 20.10. I successfully used font-manager to install a font in local storage (and font-manager seeing the two Google fonts typecatcher had installed several months ago) HOWEVER even after a couple of reboots, typecatcher is still crashing on launch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931193 Title: typecatcher crashes on launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/typecatcher/+bug/1931193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931193] [NEW] typecatcher crashes on launch
Public bug reported:
I recently upgraded to hirsute 21.04 and just discovered typecatcher
doesn't launch. A couple of web searches implies some deprecated python
issues; I don't know what version python I was running in Ubuntu 20.10.
This is what I see when trying to launch it from a terminal:
~$ typecatcher
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/typecatcher_lib/Application.py", line
30, in on_activate
self.window = TypeCatcherWindow.TypeCatcherWindow()
File "/usr/lib/python3/dist-packages/typecatcher_lib/Window.py", line 47, in
__new__
builder = get_builder('TypeCatcherWindow')
File "/usr/lib/python3/dist-packages/typecatcher_lib/helpers.py", line 44, in
get_builder
builder.add_from_file(ui_filename)
File "/usr/lib/python3/dist-packages/typecatcher_lib/Builder.py", line 86, in
add_from_file
ele_widgets = tree.getiterator("object")
AttributeError: 'ElementTree' object has no attribute 'getiterator'
~$
~$ python --version
Python 2.7.18
~$
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: typecatcher 0.3-1.2
ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
Uname: Linux 5.11.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 7 22:40:36 2021
InstallationDate: Installed on 2018-10-20 (961 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: typecatcher
UpgradeStatus: Upgraded to hirsute on 2021-05-12 (26 days ago)
** Affects: typecatcher (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931193
Title:
typecatcher crashes on launch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/typecatcher/+bug/1931193/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887993] Re: packages confirmation dialog too tall
** Summary changed: - packages confirmation dialog unnecessarily tall + packages confirmation dialog too tall -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887993 Title: packages confirmation dialog too tall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1887993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887993] Re: packages confirmation dialog unnecessarily tall
I am upgrading from Ubuntu 19.10 to 21.04 "Hirsuite Hippo," and this just "bit" me again, this time on a laptop with a "normal" screen 1366x768 resolution. MAYBE it's because I also have an old small 1014x768 external monitor set as the primary display ?? Again, it's fortunate I know how to use the "windows" key to drag the screen up because I'm given no obvious way to resize the window to fit and make the "Do You Want to Start the Upgrade" window show the "Start Upgrade" button at the bottom. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887993 Title: packages confirmation dialog unnecessarily tall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1887993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] Re: Recent update broke qemu-system-riscv64
That would explain why I could reproduce with personal builds. Glibc looks very relevant here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Recent update broke qemu-system-riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1921664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] Re: Recent update broke qemu-system-riscv64
couldN’T, grr -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Recent update broke qemu-system-riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1921664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] Re: Recent update broke qemu-system-riscv64
Small correction: everything I've done have been everything 64-bit. I don't use armhf. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Recent update broke qemu-system-riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] Re: Recent update broke qemu-system-riscv64
FWIW: I went full inception and ran QEMU/RISC-V under QEMU/RISC-V but I couldn't reproduce the issue here (that is, everything worked, but very slowly). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Recent update broke qemu-system-riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] Re: Recent update broke qemu-system-riscv64
I'm not sure how I was _supposed_ to do this, but I checked out the official release and then switch to the hirsute-delta-as-commits- lp1921664 (6c7e3708580ac50f78261a82b2fcdc2f288d6cea) branch which kept the directories around. I configured with "--target- list=riscv64-softmmu" to save time and the resulting binary did *not* reproduce the bug. So in summary: - Debian 1:5.2+dfsg-9ubuntu1 reproduces the issue of both RPi4 and my M1 VM. - So far no version I have built have reproduced the issue. Definitely makes either _how_ I built it or the _build tools_ I used sus I'm not sure what to do next. I assume I'm supposed to set the bug back to "new"? ** Changed in: qemu (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/1921664 Title: Recent update broke qemu-system-riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] Re: Recent update broke qemu-system-riscv64
Christian, I think I need some help. Like I said I couldn't build with apt source --compile qemu. I proceeded with $ git clone -b hirsute-delta-as-commits-lp1921664 git+ssh://tommy- ubuntu...@git.launchpad.net/~paelzer/ubuntu/+source/qemu (git submodule update --init did nothing) but the configure step failed with $ ../configure warn: ignoring non-existent submodule meson warn: ignoring non-existent submodule dtc warn: ignoring non-existent submodule capstone warn: ignoring non-existent submodule slirp cross containers no NOTE: guest cross-compilers enabled: cc s390x-linux-gnu-gcc cc s390x-linux-gnu-gcc /usr/bin/python3: can't open file '/home/tommy/qemu/meson/meson.py': [Errno 2] No such file or directory /usr/bin/python3: can't open file '/home/tommy/qemu/meson/meson.py': [Errno 2] No such file or directory I had no problem building the master branch so I'm not sure what's going on with the submodules in your repo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Recent update broke qemu-system-riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] Re: Recent update broke qemu-system-riscv64
On my 4 GB Raspberry Pi 4 QEMU emulator version 5.2.0 (Debian 1:5.2+dfsg-3ubuntu1) worked as expected as did, but QEMU emulator version 5.2.0 (Debian 1:5.2+dfsg-9ubuntu1) *did* reproduce the issue, but it took slightly longer to hit it (a few minutes): ``` ... [ OK ] Started Serial Getty on ttyS0. [ OK ] Reached target Login Prompts. Ubuntu 20.04 LTS Ubuntu-riscv64 ttyS0 Ubuntu-riscv64 login: qemu-system-riscv64: ../../util/qemu-coroutine-lock.c:57: qemu_co_queue_wait_impl: Assertion `qemu_in_coroutine()' failed. ./run_riscvVM.sh: line 31: 2304 Aborted (core dumped) qemu-system-riscv64 -machine virt -nographic -smp 4 -m 3G -bios fw_payload.bin -device virtio-blk-device,drive=hd0 -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-device,rng=rng0 -drive file=riscv64-UbuntuFocal-qemu.qcow2,format=qcow2,id=hd0 -device virtio-net-device,netdev=usernet -netdev user,id=usernet,$ports ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Recent update broke qemu-system-riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] Re: Recent update broke qemu-system-riscv64
> Maybe it depends on what arm platform (as there are often subtle differences) > or which storage (as > the assert is about storage) you run on. > My CPU is an X-Gene and my Storage is a ZFS (that backs my container running > hirsute and Hirsute's > qemu). > What is it for you? Sorry, I thought I had already reported that, but it's not clear. My setup is special in a couple of ways: - I'm running Ubuntu/Arm64 (21.04 beta, fully up-to-date except kernel), but ... - it's a virtual machine on a macOS/Mac Mini M1 (fully up-to-date) - It's running the 5.8.0-36-generic which isn't the latest (for complicated reasons) I'll try to bring my Raspberry Pi 4 back up on Ubuntu and see if I can reproduce it there. > Is this failing 100% of the times for you, or just sometimes and maybe racy? 100% consistently reproducible with the official packages. 0% reproducible with my own build > A hint which versions to look at can be derived from > $ grep -- qemu-system-misc /var/log/dpkg.log Alas, I had critical space issues and /var/log was among the casualties > Could you rebuild what you get with "apt source qemu". That will be 5.2 plus > the Delta we have... TIL. I tried `apt source --compile qemu` but it complains dpkg-checkbuilddeps: error: Unmet build dependencies: gcc-alpha-linux- gnu gcc-powerpc64-linux-gnu but these packages are not available [anymore?]. I don't currently have the time to figure this out. > FYI my qemu is still busy It's hung. The boot take ~ 20 seconds on my host. Multi-minutes is not normal. If I can reproduce this on a Raspberry Pi 4, then I'll proceed with your suggestions above, otherwise I'll pause this until I can run Ubuntu natively on the Mac Mini. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Recent update broke qemu-system-riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] Re: Recent update broke qemu-system-riscv64
** Changed in: qemu (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/1921664 Title: Recent update broke qemu-system-riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] Re: Recent update broke qemu-system-riscv64
Self-built v5.2.0 qemu-system-riscv64 does _not_ produce the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Recent update broke qemu-system-riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] Re: Recent update broke qemu-system-riscv64
0. Repro: $ wget https://github.com/carlosedp/riscv-bringup/releases/download/v1.0/UbuntuFocal-riscv64-QemuVM.tar.gz $ tar xzf UbuntuFocal-riscv64-QemuVM.tar.gz $ ./run_riscvVM.sh (wait ~ 20 s) [ OK ] Reached target Local File Systems (Pre). [ OK ] Reached target Local File Systems. Starting udev Kernel Device Manager... qemu-system-riscv64: ../../block/aio_task.c:64: aio_task_pool_wait_one: Assertion `qemu_coroutine_self() == pool->main_co' failed. (root password is "riscv" fwiw) 1. "Was the formerly working version 1:5.2+dfsg-6ubuntu2?" I'm afraid I don't know, but I update a few times a week. If you can tell me know to try individual versions, I'll do that 2. "full commandline you use to start your qemu test case?" Probably the repo above is more useful, but FWIW: qemu-system-riscv64 \ -machine virt \ -nographic \ -smp 4 \ -m 4G \ -bios fw_payload.bin \ -device virtio-blk-device,drive=hd0 \ -object rng-random,filename=/dev/urandom,id=rng0 \ -device virtio-rng-device,rng=rng0 \ -drive file=riscv64-UbuntuFocal-qemu.qcow2,format=qcow2,id=hd0 \ -device virtio-net-device,netdev=usernet \ -netdev user,id=usernet,$ports 3. "the same 1:5.2+dfsg-9ubuntu1 @amd64 it works fine for you? Just the emulation of riscv64 on arm64 HW is what now fails for you correct?" Yes x 2, confirmed with the above repro. $ apt-cache policy qemu qemu: Installed: 1:5.2+dfsg-9ubuntu1 Candidate: 1:5.2+dfsg-9ubuntu1 Version table: *** 1:5.2+dfsg-9ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages 100 /var/lib/dpkg/status 4. "It also is interesting that you built qemu from git to have it work. Did you build tag v5.2.0 or the latest commit?" latest. Rebuilding from the "vommit" tagged with v5.2.0 ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Recent update broke qemu-system-riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] Re: Recent update broke qemu-system-riscv64
FWIW, I just now built qemu-system-riscv64 from git ToT and that works fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Recent update broke qemu-system-riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] [NEW] Recent update broke qemu-system-riscv64
Public bug reported: I regularly run a RISC-V (RV64GC) QEMU VM, but an update a few days ago broke it. Now when I launch it, it hits an assertion: OpenSBI v0.6 _ _ / __ \ / | _ \_ _| | | | |_ __ ___ _ __ | (___ | |_) || | | | | | '_ \ / _ \ '_ \ \___ \| _ < | | | |__| | |_) | __/ | | |) | |_) || |_ \/| .__/ \___|_| |_|_/|/_| | | |_| ... Found /boot/extlinux/extlinux.conf Retrieving file: /boot/extlinux/extlinux.conf 618 bytes read in 2 ms (301.8 KiB/s) RISC-V Qemu Boot Options 1: Linux kernel-5.5.0-dirty 2: Linux kernel-5.5.0-dirty (recovery mode) Enter choice: 1:Linux kernel-5.5.0-dirty Retrieving file: /boot/initrd.img-5.5.0-dirty qemu-system-riscv64: ../../block/aio_task.c:64: aio_task_pool_wait_one: Assertion `qemu_coroutine_self() == pool->main_co' failed. ./run.sh: line 31: 1604 Aborted (core dumped) qemu-system-riscv64 -machine virt -nographic -smp 8 -m 8G -bios fw_payload.bin -device virtio-blk-devi ce,drive=hd0 -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-device,rng=rng0 -drive file=riscv64-UbuntuFocal-qemu.qcow2,format=qcow2,id=hd0 -devi ce virtio-net-device,netdev=usernet -netdev user,id=usernet,$ports Interestingly this doesn't happen on the AMD64 version of Ubuntu 21.04 (fully updated). Think you have everything already, but just in case: $ lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 $ uname -a Linux minimacvm 5.11.0-11-generic #12-Ubuntu SMP Mon Mar 1 19:27:36 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux (note this is a VM running on macOS/M1) $ apt-cache policy qemu qemu: Installed: 1:5.2+dfsg-9ubuntu1 Candidate: 1:5.2+dfsg-9ubuntu1 Version table: *** 1:5.2+dfsg-9ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports hirsute/universe arm64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: qemu 1:5.2+dfsg-9ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic aarch64 ApportVersion: 2.20.11-0ubuntu61 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Date: Mon Mar 29 02:33:25 2021 Dependencies: KvmCmdLine: COMMAND STAT EUID RUID PIDPPID %CPU COMMAND Lspci-vt: -[:00]-+-00.0 Apple Inc. Device f020 +-01.0 Red Hat, Inc. Virtio network device +-05.0 Red Hat, Inc. Virtio console +-06.0 Red Hat, Inc. Virtio block device \-07.0 Red Hat, Inc. Virtio RNG Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: console=hvc0 root=/dev/vda SourcePackage: qemu UpgradeStatus: Upgraded to hirsute on 2020-12-30 (88 days ago) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error
[Bug 1907559] Re: nvidia-kernel-source-390 390.138-0ubuntu0.20.04.1: nvidia kernel module failed to build
I am a noob at resolving this type of stuff, but I have a Dell Precision m4700. I have an Intel i7-3540m and Nvidia Quadro k2000m. I don't know how useful this is, but the battery is busted and doesn't work. Please help me resolve this problem. I can't open any gpu intensefy tasks such as games. If I try to launch them it shows this error message. Thank you for helping. ** Attachment added: "Screenshot from 2021-01-12 12-38-40.png" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1907559/+attachment/5452405/+files/Screenshot%20from%202021-01-12%2012-38-40.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907559 Title: nvidia-kernel-source-390 390.138-0ubuntu0.20.04.1: nvidia kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1907559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895199] Re: web apps no longer launch into separate windows
I believe I found the relevant Chromium bug! https://bugs.chromium.org/p/chromium/issues/detail?id=1125020 On a different system I have been trying to fix my webapps (I have not found a way to make webapps open in separate taskbar icons in Ubuntu Groovy), and was digging through Chromium bug reports. I went to chrome://flags/ and found chrome://flags/#enable-desktop-pwas-migration-user-display-mode-clean-up which specifically mentions https://crbug.com/1125020 which resolves to the link at the top. This sounds similar to what I was experiencing that broke the windowing of webapps after a software upgrade, and it's also just about the right timeframe. I'm not on the same system and may not be able to test that one but I turned on the flag and fortunately it didn't break anything. Unfortunately it hasn't fixed my other bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895199 Title: web apps no longer launch into separate windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1895199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895199] Re: web apps no longer launch into separate windows
I tried to link this bug to https://bugs.chromium.org/p/chromium/issues/detail?id=1125020 and Launchpad complained it does not recognize the bug tracker. Weird! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895199 Title: web apps no longer launch into separate windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1895199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904437] Re: Epiphany launcher broken
attaching a copy of the browsers.desktop file that the snap apparently puts in ~/.local/share/applications ** Attachment added: "browsers.desktop" https://bugs.launchpad.net/ubuntu/+source/epiphany/+bug/1904437/+attachment/5436749/+files/browsers.desktop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904437 Title: Epiphany launcher broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany/+bug/1904437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904437] [NEW] Epiphany launcher broken
Public bug reported: I just installed Epiphany for the first time in several years. I'm running Ubuntu 20.10 and got offered the snap or the flatpak. I installed the snap. The version it installed is The version number is 3.34.4-1-g606db9aec9 2020-06-05 I was disappointed that the GNOME launcher the snap installed doesn't seem to even LIST Epiphany (or GNOME Web) ... it lists the OTHER browsers I have installed (Chromium and Firefox) and a menu item to edit the launcher ... at the fixed address /home/glen/.local/share/applications This is my first attempt to report a bug against a snap so my apologies if this is the wrong place ** Affects: epiphany (Ubuntu) Importance: Undecided Status: New ** Tags: snap ** Tags added: snap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904437 Title: Epiphany launcher broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany/+bug/1904437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895199] Re: web apps no longer launch into separate windows
For step 5 above I also sometimes deleted the app from chrome://apps and re-created it. SO the actual bug on this issue seems to be some discontinuity with my old webapp definitions because I have been able to make them work again by recreating them again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895199 Title: web apps no longer launch into separate windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1895199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895199] Re: web apps no longer launch into separate windows
OK I have been digging around. I was reading https://askubuntu.com/questions/31427 hoping it would give me some clues, and it didn't HOWEVER another web search or two and I found https://askubuntu.com/questions/910494 and here's what I came up with that seems to work: 1) Open Chromium 2) navigate to chrome://apps 3) right-click on icon for the created application 4) choose "Open as Window" 5) If the window doesn't behave properly in the favorites bar, delete it from Favorites and open it again and re-add it to favorites. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895199 Title: web apps no longer launch into separate windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1895199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895199] Re: web apps no longer launch into separate windows
On the above, I have discovered that if I double-click the weird .desktop file, I get a message asking if I should trust and launch it, and when I agree to trust and launch, the name changes to the intended name AND the icon of the file changes to reflect the proper "webapp." For example, messages.google.com gains the messages icon and renames to "Messages." HOWEVER it STILL doesn't open in a separate window in my old user account. I presume there's still some cruft somewhere. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895199 Title: web apps no longer launch into separate windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1895199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895199] Re: web apps no longer launch into separate windows
(sigh) I created a new user account on my old system. I can create new windowed apps. (webapp?) I went back to my regular user account and moved ~/.config/chromium/ (514.3MB) to the desktop. I could not open existing webapp window bookmarks; they don't even go to the correct URL. There must be some stuff in there to link the bookmark to the correct URL SO I deleted the fresh .config/chromium folder and copied the desktop one back and then I used Chromium's Settings --> Advanced -- Reset Settings and ~/.config/chromium/ shrank the folder to 148MB I can get the old bookmarks to open the correct URL but they still don't open in a separate window. I also notice that when I create webapp links Chromium creates a file on my desktop called something like "~/Desktop/chrome- kjbdgfilnfhdoflbpgamdcdgpehopbep-Default.desktop" I don't remember it doing that before the recent update? If it did I must have deleted them long ago. I'm beginning to wonder if the cruft is in GNOME somewhere? I need to do some work at the moment but I'll try some more things later -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895199 Title: web apps no longer launch into separate windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1895199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895199] Re: web apps no longer launch into separate windows
I just tried it in a fresh Bionic VM and yes it worked there. When I get back to the other machine I'll see if there's some cruft in ~/.config/chromium/ or somewhere else. That hard drive has been running Ubuntu for a decade or more so there's plenty of cruft to choose from. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895199 Title: web apps no longer launch into separate windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1895199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895199] [NEW] web apps no longer launch into separate windows
Public bug reported: Chromium-browser updated on my system yesterday and today I noticed that unlike the previous version (84.0.4147.105-0ubuntu0.18.04.1) when I click my "favorite" shortcuts for Google Messages, Google Contacts, Google Calendar, and a website for a local radio station, the "app" shortcuts no longer create separate independent windows, but instead open a new tab in a Chromium browser window. Strangely enough, the web app shortcut for GMail still opens correctly in a separate browser window. As I mentioned, this seems to be a regression from version 84.0.4147.105-0ubuntu0.18.04.1 which got installed on my system yesterday. I am concerned because broken webapps is one of several features I will miss when I must upgrade this system from bionic. (I have another system running 20.04 and of course the snap version of Chromium does not do web apps reliably nor does the snap version work with the KeePassXC plugin.) Just in case this is just an incompatibility with existing shortcuts, I just created a NEW shortcut for the radio station web site and the new shortcut exhibits the same behavior. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 85.0.4183.83-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 10 14:10:26 2020 DetectedPlugins: InstallationDate: Installed on 2020-04-07 (156 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.chromium-browser: [deleted] ** Affects: chromium-browser (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/1895199 Title: web apps no longer launch into separate windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1895199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895199] Re: web apps no longer launch into separate windows
I meant to say the previous version running on my system was 84.0.4147.105-0ubuntu0.18.04.1 The new version with the regression is 85.0.4183.83-0ubuntu0.18.04.2 (I got these versions from /var/apt/history.log ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895199 Title: web apps no longer launch into separate windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1895199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890858] Re: AppArmor profile causes QEMU/KVM - Not Connected
Okay so I did aa-complain on the libvirt profile and sudo aa-logprof when running "virsh list". It generated a new profile which I'll be attaching here When running with that enabled I think it works.. I'm able to do virsh list as a normal user. Unless I'm doing something wrong and misunderstanding.. Have not compared the original to this yet because the diff was long. But it would be interesting to hear if it works for others. ** Attachment added: "aa-logprof generated libvirt profile" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1890858/+attachment/5402216/+files/usr.sbin.libvirtd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890858 Title: AppArmor profile causes QEMU/KVM - Not Connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1890858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890858] Re: AppArmor profile causes QEMU/KVM - Not Connected
I'm having the same issue on an upgraded 18.04 -> 20.04.
This is bugging me immensely.
Ready to help out in any way. I have also confirmed that if I disable
apparmor it works. But that is not a solution.
Here is an strace showing what it's up to starting at the socket access.
$ VIRSH_DEBUG=0 strace virsh list
...
access("/var/run/libvirt/virtqemud-sock", F_OK) = -1 ENOENT (No such file or
directory)
access("/var/run/libvirt/libvirt-sock", F_OK) = 0
socket(AF_UNIX, SOCK_STREAM, 0) = 6
connect(6, {sa_family=AF_UNIX, sun_path="/var/run/libvirt/libvirt-sock"}, 110)
= 0
getsockname(6, {sa_family=AF_UNIX}, [128->2]) = 0
futex(0x7f22454da060, FUTEX_WAKE_PRIVATE, 2147483647) = 0
fcntl(6, F_GETFD) = 0
fcntl(6, F_SETFD, FD_CLOEXEC) = 0
fcntl(6, F_GETFL) = 0x2 (flags O_RDWR)
fcntl(6, F_SETFL, O_RDWR|O_NONBLOCK)= 0
futex(0x7f22454da180, FUTEX_WAKE_PRIVATE, 2147483647) = 0
pipe2([7, 8], O_CLOEXEC)= 0
write(5, "\0", 1) = 1
futex(0x7f22454d9320, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x7f22454da078, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7f22454da150, FUTEX_WAKE_PRIVATE, 2147483647) = 0
write(5, "\0", 1) = 1
futex(0x7f22454d9320, FUTEX_WAKE_PRIVATE, 1) = 1
rt_sigprocmask(SIG_BLOCK, [PIPE CHLD WINCH], [], 8) = 0
poll([{fd=6, events=POLLOUT}, {fd=7, events=POLLIN}], 2, -1) = 1 ([{fd=6,
revents=POLLOUT}])
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
write(6, "\0\0\0\34 \0\200\206\0\0\0\1\0\0\0B\0\0\0\0\0\0\0\0\0\0\0\0", 28) = 28
rt_sigprocmask(SIG_BLOCK, [PIPE CHLD WINCH], [], 8) = 0
poll([{fd=6, events=POLLIN}, {fd=7, events=POLLIN}], 2, -1) = 1 ([{fd=6,
revents=POLLIN|POLLHUP}])
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
read(6, "", 4) = 0
openat(AT_FDCWD, "/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 9
fstat(9, {st_mode=S_IFREG|0644, st_size=2996, ...}) = 0
read(9, "# Locale name alias data base.\n#"..., 4096) = 2996
read(9, "", 4096) = 0
close(9)= 0
openat(AT_FDCWD, "/usr/share/locale/en_US/LC_MESSAGES/libvirt.mo", O_RDONLY) =
-1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en/LC_MESSAGES/libvirt.mo", O_RDONLY) = -1
ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale-langpack/en_US/LC_MESSAGES/libvirt.mo",
O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale-langpack/en/LC_MESSAGES/libvirt.mo",
O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en_US/LC_MESSAGES/libc.mo", O_RDONLY) = -1
ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en/LC_MESSAGES/libc.mo", O_RDONLY) = -1
ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale-langpack/en_US/LC_MESSAGES/libc.mo",
O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale-langpack/en/LC_MESSAGES/libc.mo", O_RDONLY)
= -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/charset.alias", O_RDONLY) = -1
ENOENT (No such file or directory)
write(5, "\0", 1) = 1
futex(0x7f22454d9320, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x55589445f510, FUTEX_WAKE_PRIVATE, 1) = 1
close(6)= 0
close(8)= 0
close(7)= 0
write(2, "error: ", 7error: ) = 7
write(2, "failed to connect to the hypervi"..., 36failed to connect to the
hypervisor
) = 36
write(2, "error: ", 7error: ) = 7
write(2, "End of file while reading data: "..., 51End of file while reading
data: Input/output error
) = 51
write(1, "\n", 1
) = 1
write(5, "\0", 1) = 1
futex(0x7f22454d9320, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x7fff571d7ca0, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x7f2240d6b9d0, FUTEX_WAIT, 134641, NULL) = 0
exit_group(1) = ?
+++ exited with 1 +++
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890858
Title:
AppArmor profile causes QEMU/KVM - Not Connected
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1890858/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887993] [NEW] packages confirmation dialog unnecessarily tall
Public bug reported: Every time I upgrade to a new release of ubuntu on this netbook (screen size 1024x600) the upgrader churns away collecting its information and then when it presents the dialog with the packages to remove, not upgradeable, and packages to upgrade. UNFORTUNATELY the buttons at the bottom of the dialog are not visible because there's WAY too much empty space in the dialog. I have to know to alt-drag the dialog up to get to the buttons. The dialog gets even bigger when I open the right-triangles to look at the lists, and does not shrink when I collapse the lists again. I would hope the dialog could better handle a short netbook screen. I don't remember at the moment but I believe I have also seen this same issue on my "ordinary" sized laptop screen, but the buttons on the dialog start out at a good size but the dialog gets too tall after opening the lists as described above. The dialog does not shrink itself to fit the screen. I just ran ubuntu-bug while upgrading xubuntu from 19.10 to 20.04. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Fri Jul 17 12:27:06 2020 InstallationDate: Installed on 2018-08-14 (703 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2020-07-17 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade eoan third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887993 Title: packages confirmation dialog unnecessarily tall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1887993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886705] [NEW] ratbagd, segrault
Public bug reported: This bug is fixed upstream. Described in the linked github issue. $ sudo ratbagd --verbose=raw Initializing libratbag ratbag debug: New device: Logitech M705 ratbag debug: Using data directory '/usr/share/libratbag' ratbag debug: device assigned driver hidpp10 ratbag debug: hidraw info: bus 0x03 vendor 0x46d product 0x101b ratbag debug: Logitech M705 is device '/dev/hidraw2'. ratbag debug: Parsing HID report descriptor ratbag debug: Parsing HID report descriptor ratbag debug: - HID report ID 02 ratbag debug: - HID report ID 10 ratbag debug: - HID report ID 11 ratbag debug: - HID report ID 20 ratbag debug: - HID report ID 21 ratbag raw: Fetching individual features (0x1) ratbag raw: hidpp10 tx: 10 | 00 | 81 | 01 | 00 00 00 ratbag raw: hidpp write: 10 00 81 01 00 00 00 ratbag raw: hidpp read: 10 01 81 01 42 00 00 ratbag raw: hidpp10 rx: 10 | 00 | 81 | 01 | 42 00 00 ratbag raw: Fetching HID++ notifications (00) ratbag raw: hidpp10 tx: 10 | 00 | 81 | 00 | 00 00 00 ratbag raw: hidpp write: 10 00 81 00 00 00 00 ratbag raw: hidpp read: 10 01 81 00 10 00 00 ratbag raw: hidpp10 rx: 10 | 00 | 81 | 00 | 10 00 00 ratbag raw: Fetching current resolution (0x63) ratbag raw: hidpp10 tx: 10 | 00 | 83 | 63 | 00 00 00 ratbag raw: hidpp write: 10 00 83 63 00 00 00 ratbag raw: hidpp read: 10 01 8f 83 63 01 00 ratbag raw: HID++ error from the device (0): ERR_INVALID_SUBID (01) ratbag raw: hidpp10 rx: 10 | 00 | 8f | 83 | 63 01 00 ratbag raw: Fetching LED status (0x51) ratbag raw: hidpp10 tx: 10 | 00 | 81 | 51 | 00 00 00 ratbag raw: hidpp write: 10 00 81 51 00 00 00 ratbag raw: hidpp read: 10 01 8f 81 51 02 00 ratbag raw: HID++ error from the device (0): ERR_INVALID_ADDRESS (02) ratbag raw: hidpp10 rx: 10 | 00 | 8f | 81 | 51 02 00 ratbag raw: Fetching USB refresh rate (0x64) ratbag raw: hidpp10 tx: 10 | 00 | 81 | 64 | 00 00 00 ratbag raw: hidpp write: 10 00 81 64 00 00 00 ratbag raw: hidpp read: 10 01 8f 81 64 02 00 ratbag raw: HID++ error from the device (0): ERR_INVALID_ADDRESS (02) ratbag raw: hidpp10 rx: 10 | 00 | 8f | 81 | 64 02 00 ratbag raw: Fetching optical sensor settings (0x61) ratbag raw: hidpp10 tx: 10 | 00 | 81 | 61 | 00 00 00 ratbag raw: hidpp write: 10 00 81 61 00 00 00 ratbag raw: hidpp read: 10 01 8f 81 61 02 00 ratbag raw: HID++ error from the device (0): ERR_INVALID_ADDRESS (02) ratbag raw: hidpp10 rx: 10 | 00 | 8f | 81 | 61 02 00 ratbag raw: Fetching current profile (0xf) ratbag raw: hidpp10 tx: 10 | 00 | 81 | 0f | 00 00 00 ratbag raw: hidpp write: 10 00 81 0f 00 00 00 ratbag raw: hidpp read: 10 01 8f 81 0f 02 00 ratbag raw: HID++ error from the device (0): ERR_INVALID_ADDRESS (02) ratbag raw: hidpp10 rx: 10 | 00 | 8f | 81 | 0f 02 00 ratbag error: Failed to get HID++1.0 device for Logitech M705 ratbag error: libratbag bug: Logitech M705: invalid number of profiles (0) Segmentation fault ** Affects: libratbag Importance: Unknown Status: Unknown ** Affects: libratbag (Ubuntu) Importance: Undecided Status: Confirmed ** Bug watch added: github.com/libratbag/piper/issues #515 https://github.com/libratbag/piper/issues/515 ** Also affects: libratbag via https://github.com/libratbag/piper/issues/515 Importance: Unknown Status: Unknown ** No longer affects: libratbag ** Bug watch added: github.com/libratbag/libratbag/issues #970 https://github.com/libratbag/libratbag/issues/970 ** Also affects: libratbag via https://github.com/libratbag/libratbag/issues/970 Importance: Unknown Status: Unknown ** Changed in: libratbag (Ubuntu) Status: New => Confirmed ** Description changed: + This bug is fixed upstream. Described in the linked github issue. + $ sudo ratbagd --verbose=raw Initializing libratbag ratbag debug: New device: Logitech M705 ratbag debug: Using data directory '/usr/share/libratbag' ratbag debug: device assigned driver hidpp10 ratbag debug: hidraw info: bus 0x03 vendor 0x46d product 0x101b ratbag debug: Logitech M705 is device '/dev/hidraw2'. ratbag debug: Parsing HID report descriptor ratbag debug: Parsing HID report descriptor ratbag debug: - HID report ID 02 ratbag debug: - HID report ID 10 ratbag debug: - HID report ID 11 ratbag debug: - HID report ID 20 ratbag debug: - HID report ID 21 ratbag raw: Fetching individual features (0x1) ratbag raw: hidpp10 tx: 10 | 00 | 81 | 01 | 00 00 00 ratbag raw: hidpp write: 10 00 81 01 00 00 00 ratbag raw: hidpp read: 10 01 81 01 42 00 00 ratbag raw: hidpp10 rx: 10 | 00 | 81 | 01 | 42 00 00 ratbag raw: Fetching HID++ notifications (00) ratbag raw: hidpp10 tx: 10 | 00 | 81 | 00 | 00 00 00 ratbag raw: hidpp write: 10 00 81 00 00 00 00 ratbag raw: hidpp read: 10 01 81 00 10 00 00 ratbag raw: hidpp10 rx: 10 | 00 | 81 | 00 | 10 00 00 ratbag raw: Fetching current resolution (0x63) ratbag raw: hidpp10 tx: 10 | 00 | 83 | 63 | 00 00 00 ratbag raw: hidpp write: 10
[Bug 1869587] Re: WiFi performance is slow
Thinkpad X1C6 20.04, 5.4.0-33-generic, had to remove backport-iwlwifi- dkms to get back usable wifi. This dmesg is after removing the dkms: $ dmesg |grep -i iwl |grep -v "HW address" [ 41.918069] iwlwifi :02:00.0: Found debug destination: EXTERNAL_DRAM [ 41.918071] iwlwifi :02:00.0: Found debug configuration: 0 [ 41.919074] iwlwifi :02:00.0: loaded firmware version 36.77d01142.0 op_mode iwlmvm [ 42.009330] iwlwifi :02:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230 [ 42.019052] iwlwifi :02:00.0: Applying debug destination EXTERNAL_DRAM [ 42.019365] iwlwifi :02:00.0: Allocated 0x0040 bytes for firmware monitor. [ 42.158286] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' [ 42.185772] iwlwifi :02:00.0 wlp2s0: renamed from wlan0 [ 44.074867] iwlwifi :02:00.0: Applying debug destination EXTERNAL_DRAM [ 44.212564] iwlwifi :02:00.0: Applying debug destination EXTERNAL_DRAM [ 44.280191] iwlwifi :02:00.0: FW already configured (0) - re-configuring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869587 Title: WiFi performance is slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1869587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877812] [NEW] package sendmail-bin 8.15.2-13 failed to install/upgrade: installed sendmail-bin package post-installation script subprocess returned error exit status 2
Public bug reported: when i update to ubuntu i got this error ProblemType: Package DistroRelease: Ubuntu 19.10 Package: sendmail-bin 8.15.2-13 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Sat May 9 18:39:09 2020 ErrorMessage: installed sendmail-bin package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2018-05-12 (729 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: sendmail Title: package sendmail-bin 8.15.2-13 failed to install/upgrade: installed sendmail-bin package post-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to eoan on 2020-05-10 (0 days ago) ** Affects: sendmail (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877812 Title: package sendmail-bin 8.15.2-13 failed to install/upgrade: installed sendmail-bin package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sendmail/+bug/1877812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860313] Re: megaraid_sas fails after rtcwake
The issue appears to be fixed in Mainline Kernel 5.6.6. So far, I have not done further research, when this fix was implemented excatly. If needed, I can do further mainline or -rc tests. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860313 Title: megaraid_sas fails after rtcwake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1860313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 701856] Re: Brother's printer/scanner drivers awkward to find and install
UPDATE: On a freshly installed Bionic (minimal install) system I also
had to install libusb-0.1-4
This procedure worked for me to get a Brother DCP-7020 scanner working in
Ubuntu 18.04 Bionic.
For this procedure the user is "bob"
1) Install the latest brscan2 package (I have brscan2-0.2.5-1.amd64.deb
which I downloaded in 2014)
2) Manually link the drivers brscan2 installed into /usr/lib/x86_64
-linux-gnu/sane/ and /usr/lib/x86_64-linux-gnu/
[Note that in /usr/lib64/sane/ BOTH libsane-brother2.so and
libsane.brother2.so.1 both link to libsane-brother2.so.1.0.7 so the
others could all link to that one file but this is easier.]
bob:~$ cd /usr/lib/x86_64-linux-gnu/sane
$ sudo ln -sf /usr/lib64/sane/libsane-brother2.so
$ sudo ln -sf /usr/lib64/sane/libsane-brother2.so.1
$ sudo ln -sf /usr/lib64/sane/libsane-brother2.so.1.0.7
bob:/usr/lib/x86_64-linux-gnu/sane$ cd ..
(now in directory /usr/lib/x86_64-linux-gnu/ )
$ sudo ln -sf /usr/lib64/libbrcolm2.so
$ sudo ln -sf /usr/lib64/libbrcolm2.so.1
$ sudo ln -sf /usr/lib64/libbrcolm2.so.1.0.1
$ sudo ln -sf /usr/lib64/libbrscandec2.so
$ sudo ln -sf /usr/lib64/libbrscandec2.so.1
$ sudo ln -sf /usr/lib64/libbrscandec2.so.1.0.0
3) Install this libusb library (if it's missing)
$ sudo apt install libusb-0.1-4
4) At this point scanimage -L should detect the scanner when run as
root.
$ sudo scanimage -L
4a) If it doesn't work and especially if you're running something other
than Ubuntu Bionic, you might make verify SANE is looking in the right
directory using the debug flag and see where it's not finding the pieces
it needs
$ SANE_DEBUG_DLL=128 scanimage -L
5) Create a udev file so the scanner is accessible to a scanner group
$ sudo gedit /lib/udev/rules.d/96-brother-scanner.rules
-- with the following contents:
# Brother DCP-7020 scanner
SUBSYSTEMS=="usb" \
, ATTRS{idVendor}=="04f9" \
, ATTRS{idProduct}=="0183" \
, ACTION=="add", \
, MODE="0664", \
, GROUP="scanner" \
, ENV{libsane_matched}="yes"
# note this udev instruction ends lines with \
# backslash so the single comma-separated
# udev command is not crammed onto one line.
# END OF FILE
6) Add the user bob to the scanner group (as specified in the udev file
above):
$ sudo adduser bob scanner
7) If you're bob and you weren't already in the group you'll have to log
out and back in, or reboot the system. To reload udev:
$ sudo udevadm control --reload-rules
--> Everything should work after you reboot / login / reload. Yay.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/701856
Title:
Brother's printer/scanner drivers awkward to find and install
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/701856/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860313] Re: megaraid_sas fails after rtcwake
I also tried 5.3.0-29 by downloading the eoan packages: 5.3.0-29-generic #31-Ubuntu SMP Fri Jan 17 17:27:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ** Attachment added: "full output of journal for 5.3.0-29-generic #31-Ubuntu" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1860313/+attachment/5323481/+files/journal_5.3.0-29-generic.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860313 Title: megaraid_sas fails after rtcwake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1860313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860313] Re: megaraid_sas fails after rtcwake
latest kernel in proposed for bionic I could find: 5.3.0-28-generic #30~18.04.1-Ubuntu bug still present. ** Attachment added: "full output of journal for 5.3.0-28-generic #30~18.04.1-Ubuntu" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1860313/+attachment/5323480/+files/journal_5.3.0-28-generic.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860313 Title: megaraid_sas fails after rtcwake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1860313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860313] Re: megaraid_sas fails after rtcwake
Sorry I was out of office until today. Please find the logs attached. bug still present in 5.5.0-050500-generic #202001262030 ** Attachment added: "full output of journal for 5.5.0-050500-generic #202001262030" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1860313/+attachment/5323479/+files/journal_5.5.0_ml.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860313 Title: megaraid_sas fails after rtcwake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1860313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847069] Re: [snap] Chromium snap starts slowly
APT forced me to stop using the DEB version and start using the Snap version and I can confirm it is much slower to start on Ubuntu 19.10 (5.3.0-26) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847069 Title: [snap] Chromium snap starts slowly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1847069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860313] Re: megaraid_sas fails after rtcwake
bug not present in 18.04 original kernel tree 4.15.0-74 ** Attachment added: "full output of journal for 4.15.0-74" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1860313/+attachment/5321671/+files/megasas_4.15.0-74.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860313 Title: megaraid_sas fails after rtcwake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1860313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860313] Re: megaraid_sas fails after rtcwake
bug also present in 5.5.0-050500rc7-generic #202001192030 ** Attachment added: "megasas_rc.txt" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1860313/+attachment/5321668/+files/megasas_rc.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860313 Title: megaraid_sas fails after rtcwake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1860313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860313] [NEW] megaraid_sas fails after rtcwake
Public bug reported: It appears that in recent Kernel versions the megaraid_sas cannot properly handle suspend to RAM (rtcwake -m mem -s 30). After the system wakes up, the megaraid_sas driver reports multiple errors and I/O to disks fails completely. A reset is required to make the machine work again. ->%- Jan 20 08:54:23 Ubuntu-1804-bionic-64-minimal kernel: megaraid_sas :18:00.0: Failed to register IRQ for vector 64. Jan 20 08:54:23 Ubuntu-1804-bionic-64-minimal kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0xb0 returns -19 Jan 20 08:54:23 Ubuntu-1804-bionic-64-minimal kernel: PM: Device :18:00.0 failed to resume async: error -19 -%<- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-26-generic 5.3.0-26.28~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Mon Jan 20 09:03:49 2020 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 ** Attachment added: "full output of journal" https://bugs.launchpad.net/bugs/1860313/+attachment/5321664/+files/megasas.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860313 Title: megaraid_sas fails after rtcwake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1860313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854758] [NEW] duplicity crashes since upgraded to 19.10
Public bug reported: The following script is used to run duplicity for backup # Version PA01/01 by T Pollák on 2018-11-02 # This script is used to create a full backup of this computer # and must be run as root. # The script will run the backup command duplicity to create # a full backup on My Book Live as IP 192.168.1.100 with ftp # into the directory 64HP in the share Tommy. # The script is developed from the script backup_duplicity_full64. # To create incremental backups run the script # /home/tpollak/bin/backup_duplicity_incrHP as root. # - - - - - - PASSPHRASE=*** FTP_PASSWORD= export PASSPHRASE FTP_PASSWORD duplicity full --force --volsize 1000 --exclude /media/OS/Program\ Files/WindowsApps --exclude /media/OS/Windows --exclude /boot --exclude /cdrom --exclude /dev --exclude /proc --exclude /sys --exclude /tmp --exclude /home/tpollak/.gvfs --exclude /run/user/1000/gvfs --exclude /home/tpollak/Downloads --exclude /home/tpollak/Trash / ftp://Tommy@192.168.1.100/Tommy/64HP This looks like the following in the terminal ~$ sudo bin/backup_duplicity_fullHP LFTP version is 4.8.4 Local and Remote metadata are synchronized, no sync needed. Last full backup date: Tue Oct 1 11:56:24 2019 Traceback (innermost last): File "/usr/bin/duplicity", line 107, in with_tempdir(main) File "/usr/bin/duplicity", line 93, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1535, in main do_backup(action) File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1659, in do_backup full_backup(col_stats) File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 565, in full_backup globals.backend) File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 422, in write_multivol globals.volsize) File "/usr/lib/python3/dist-packages/duplicity/gpg.py", line 393, in GPGWriteFile data = block_iter.__next__().data File "/usr/lib/python3/dist-packages/duplicity/diffdir.py", line 542, in __next__ result = self.process(next(self.input_iter)) # pylint: disable=assignment-from-no-return File "/usr/lib/python3/dist-packages/duplicity/diffdir.py", line 680, in process data, last_block = self.get_data_block(fp) File "/usr/lib/python3/dist-packages/duplicity/diffdir.py", line 707, in get_data_block buf = fp.read(read_size) File "/usr/lib/python3/dist-packages/duplicity/diffdir.py", line 449, in read buf = self.infile.read(length) File "/usr/lib/python3/dist-packages/duplicity/diffdir.py", line 417, in read log.Warn(_(u"Error %s getting delta for %s") % (str(ex), self.infile.uc_name)) AttributeError: '_io.BufferedReader' object has no attribute 'uc_name' ~$ Below is an excerpt from a listing of the backup directory .. ftp> open 192.168.1.100 ftp> cd Tommy/64HP ftp> ls .. -rwxr-xr-x1 ftp ftp 1048607916 Dec 01 23:38 duplicity-full.20191201T135308Z.vol102.difftar.gpg -rwxr-xr-x1 ftp ftp 1048616177 Dec 01 23:43 duplicity-full.20191201T135308Z.vol103.difftar.gpg -rwxr-xr-x1 ftp ftp 1048608039 Dec 01 23:47 duplicity-full.20191201T135308Z.vol104.difftar.gpg -rwxr-xr-x1 ftp ftp 504667096 Dec 01 23:49 duplicity-full.20191201T135308Z.vol105.difftar.gpg -rwxr-xr-x1 ftp ftp 1048619424 Dec 01 15:49 duplicity-full.20191201T135308Z.vol11.difftar.gpg ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: duplicity 0.8.04-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Dec 2 15:16:02 2019 InstallationDate: Installed on 2018-10-12 (415 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: duplicity UpgradeStatus: Upgraded to eoan on 2019-10-29 (33 days ago) ** Affects: duplicity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854758 Title: duplicity crashes since upgraded to 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1854758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849527] [NEW] Should depend on libsox-fmt-mp3
Public bug reported: bmp-tag, when libsox-fmt-mp3 isn't installed, silently (wrongly) reports and tags mp3s as 146bpm. The fix is to install libsox-fmt-mp3, and unless the root bug is fixed upstream, a sensible fix would be to have the package depend on that library. I found the fix here: https://github.com/meridius/bpmwrap/issues/1 ** Affects: bpm-tools (Ubuntu) Importance: Undecided Status: New ** Tags: packaging unmetdeps -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849527 Title: Should depend on libsox-fmt-mp3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bpm-tools/+bug/1849527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849527] Re: Should depend on libsox-fmt-mp3
Oh, I'm on Disco, Ubuntu 19.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849527 Title: Should depend on libsox-fmt-mp3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bpm-tools/+bug/1849527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842098] [NEW] Cannot put insertion point before first character unless line numbers visible
Public bug reported: I recently upgraded this laptop to 19.04 and noticed that this version of Gedit has an invisible "no insertion zone" between the documents list on the left and the first character (first column) of text on every line, so that (at least on this system) there's no way to use the mouse/trackpad pointer to click and put the insertion point BEFORE the first character on any line. Anything to the left of the second character turns into a "change width" cursor. I was having to click to put the insertion point wherever it would go (usually between the first and second character) and look on this laptop keyboard for the arrow key, then arrow back into the first character position. This situation also makes it impossible to select entire lines by clicking and dragging, because the first line will always exclude the first character. I suppose this is the most annoying one, because if there's a keyboard shortcut for expanding a selection I can never recall it. The easiest workaround I have found is to turn on the display of line numbers = Preferences --> View --> Display Line Numbers This gives plenty of room to click the beginning of any lines, but of course if I'm editing prose the line numbers are a distraction. BY THE WAY I am using the default setting "system fixed width font" which the preferences panel describes as Ubuntu Mono 13. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gedit 3.32.0-3 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 30 10:16:39 2019 InstallationDate: Installed on 2018-10-20 (313 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gedit UpgradeStatus: Upgraded to disco on 2019-06-17 (73 days ago) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "screenshots with pointers" https://bugs.launchpad.net/bugs/1842098/+attachment/5285809/+files/gedit%20pointers.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842098 Title: Cannot put insertion point before first character unless line numbers visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1842098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826629] Re: deepin-screenshot: can't find dxcb Qt plugin
Yes, this new proposed package successfully fixed the issue, at least for me, on deepin-music -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826629 Title: deepin-screenshot: can't find dxcb Qt plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deepin-qt5dxcb-plugin/+bug/1826629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747463] Re: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X
I have the same issue on Radeon 570 4gb, Ryzen 1700, MSI Tomahawk on 18.04. The only way to boot is to use IOMMU=soft. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747463 Title: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1747463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827328] [NEW] ModemManager does not honor blacklisted ttys (ID_MM_DEVICE_IGNORE)
Public bug reported:
In Ubuntu 19.04 (and likely earlier) Modem Manager is installed with
filter policy 'strict' as opposed to 'default', which actually makes
Modem Manager _less_ strict regarding explicitly blacklisted ttys (see
man modemmanager).
This means that ttys, that are explicitly blacklisted from Modem Manager
by using ENV{ID_MM_DEVICE_IGNORE}="1" in its udev rule is still opened
and probed by Modem Manager although it should not.
This is a common cause of problems and frustrations for people working
with actual serial devices, e.g. within embedded development (e.g.
Arduino and the like). See https://nick.zoic.org/art/failed-to-set-dtr-
rts-systemd-modemmanager/ for an example.
A proposed solution is to change the following line in:
/lib/systemd/system/ModemManager.service
from:
ExecStart=/usr/sbin/ModemManager --filter-policy=strict
to:
ExecStart=/usr/sbin/ModemManager --filter-policy=paranoid
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: modemmanager 1.10.0-1 [modified:
lib/systemd/system/ModemManager.service]
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu May 2 15:35:58 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-05-26 (340 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: modemmanager
UpgradeStatus: Upgraded to disco on 2019-04-18 (13 days ago)
** Affects: modemmanager (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827328
Title:
ModemManager does not honor blacklisted ttys (ID_MM_DEVICE_IGNORE)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1827328/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1713615] Re: ttf-mscorefonts-installer fails because Redirection from https to http is forbidden
If you do it multiple times you will end up on a mirror after a while that does not do the redirection to http.. On April 27, 2019 5:03:54 PM GMT+02:00, Lastique <1713...@bugs.launchpad.net> wrote: >This workaround: > >sudo apt purge ttf-mscorefonts-installer && sudo apt install >--reinstall >ttf-mscorefonts-installer > >does *not* fix the installation on Disco for me. I'm assuming it may >fix >the problem for some if the redirection from https to http does not >happen for some reason. > >I'm able to install the Debian package from here: >https://packages.debian.org/buster/ttf-mscorefonts-installer > >The bug is present in at least 2 Ubuntu releases while the fix in >Debian >is available for all this time. This is... disappointing. > >-- >You received this bug notification because you are subscribed to the >bug >report. >https://bugs.launchpad.net/bugs/1713615 > >Title: > ttf-mscorefonts-installer fails because Redirection from https to http > is forbidden > >To manage notifications about this bug go to: >https://bugs.launchpad.net/ubuntu/+source/msttcorefonts/+bug/1713615/+subscriptions -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713615 Title: ttf-mscorefonts-installer fails because Redirection from https to http is forbidden To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msttcorefonts/+bug/1713615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826624] [NEW] package apt-utils 1.2.31 failed to install/upgrade: package apt-utils is already installed and configured
Public bug reported: Just installed Ubuntu 16 on an old Dell previously running Windows XP Home Edition. Deleted Windows and proceeded to become your newest Linux user. Runs okay except after shut down. Tried using Ubuntu Software for updates and had to end up using terminal to update. Had system error codes evey since. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apt-utils 1.2.31 ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-48-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: i386 Date: Fri Apr 26 19:36:41 2019 DuplicateSignature: package:apt-utils:1.2.31 Processing triggers for dbus (1.10.6-1ubuntu3.3) ... dpkg: error processing package udev (--configure): package udev is already installed and configured ErrorMessage: package apt-utils is already installed and configured InstallationDate: Installed on 2019-04-26 (0 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: dpkg Title: package apt-utils 1.2.31 failed to install/upgrade: package apt-utils is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826624 Title: package apt-utils 1.2.31 failed to install/upgrade: package apt-utils is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1826624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 701856] Re: Brother's printer/scanner drivers awkward to find and install
Here's a procedure that worked for me in Ubuntu 18.04 Bionic.
For this procedure the user is "bob"
1) Install the latest brscan2 package (I have brscan2-0.2.5-1.amd64.deb
which I downloaded in 2014)
2) Manually link the drivers brscan2 installed into /usr/lib/x86_64
-linux-gnu/sane/ and /usr/lib/x86_64-linux-gnu/
bob:~$ cd /usr/lib/x86_64-linux-gnu/sane
bob:/usr/lib/x86_64-linux-gnu/sane$ sudo ln -sf /usr/lib64/sane
/libsane-brother2.so
[sudo] password for bob:
bob:/usr/lib/x86_64-linux-gnu/sane$ sudo ln -sf
/usr/lib64/sane/libsane-brother2.so.1
bob:/usr/lib/x86_64-linux-gnu/sane$ sudo ln -sf
/usr/lib64/sane/libsane-brother2.so.1.0.7
bob:/usr/lib/x86_64-linux-gnu/sane$ cd ..
bob:/usr/lib/x86_64-linux-gnu$ sudo ln -sf /usr/lib64/libbrcolm2.so
bob:/usr/lib/x86_64-linux-gnu$ sudo ln -sf /usr/lib64/libbrcolm2.so.1
bob:/usr/lib/x86_64-linux-gnu$ sudo ln -sf /usr/lib64/libbrcolm2.so.1.0.1
bob:/usr/lib/x86_64-linux-gnu$ sudo ln -sf /usr/lib64/libbrscandec2.so
bob:/usr/lib/x86_64-linux-gnu$ sudo ln -sf /usr/lib64/libbrscandec2.so.1
bob:/usr/lib/x86_64-linux-gnu$ sudo ln -sf /usr/lib64/libbrscandec2.so.1.0.0
3) At this point scanimage -L should detect the scanner when run as root.
$ sudo scanimage -L
3a) If it doesn't work and especially if you're running something other
than Ubuntu Bionic, you might make verify SANE is looking in the right
directory using the debug flag
$ SANE_DEBUG_DLL=128 scanimage -L
4) Create a udev file so the scanner is accessible to a scanner group
$ sudo gedit /lib/udev/rules.d/96-brother-scanner.rules
-- with the following contents:
# Brother DCP-7020 scanner
SUBSYSTEMS=="usb" \
, ATTRS{idVendor}=="04f9" \
, ATTRS{idProduct}=="0183" \
, ACTION=="add", \
, MODE="0664", \
, GROUP="scanner" \
, ENV{libsane_matched}="yes"
# note this udev instruction ends lines with \
# backslash so the single comma-separated
# udev command is not crammed onto one line.
# END OF FILE
5) Add the user bob to the scanner group (as specified in the udev file above):
$ sudo adduser bob scanner
6) If you're bob and you weren't already in the group you'll have to log
out and back in, or reboot the system. To reload udev:
$ sudo udevadm control --reload-rules
--> Everything should work after you reboot / login / reload. Yay.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/701856
Title:
Brother's printer/scanner drivers awkward to find and install
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/701856/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821439] Re: speech-dispatcher produces sound errors in Firefox
*** This bug is a duplicate of bug 1736222 *** https://bugs.launchpad.net/bugs/1736222 ** This bug has been marked a duplicate of bug 1736222 speech-dispatcher distorts all sound -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821439 Title: speech-dispatcher produces sound errors in Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1821439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 701856] Re: Brother's printer/scanner drivers awkward to find and install
I just upgraded to from Xenial 16.04 to Bionic 18.04 and unfortunately the scanner broke again. Unfortunately the changes affect two places -- udev seems to have made big changes to the scanner section, so I wrote a completely new udev file, and the sane-dll backend doesn't look in the same directory. I composed my new udev script, then after lots of tinkering and some judicious use of the debug command: $ SANE_DEBUG_DLL=128 scanimage -L I discovered the changes to the sane-dll backend. I installed an instance of Trusty 14.04 and used the above command to confirm Trusty looked for brother2 in: /usr/lib/x86_64-linux-gnu/sane /usr/lib/sane Bionic ONLY looks for brother2 in: /usr/lib/x86_64-linux-gnu/sane I manually linked the files the brscan2 .deb installs into /usr/lib/x86_64-linux-gnu/sane/ and /usr/lib/x86_64-linux-gnu/ into /usr/lib/x86_64-linux-gnu/sane/ and /usr/lib/x86_64-linux-gnu/ and it seems to work. I will attempt to write up a procedure (for my benefit if nothing else). But it may take me a little while. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/701856 Title: Brother's printer/scanner drivers awkward to find and install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/701856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821642] [NEW] stalls during install or reports an error that the CD might be currupt
Public bug reported: my next step is to use the live disc as the OS and download the current version then burn a new disc before I reboot. This is my home server that is used mainly for live broadcasting to my streaming server radio1.440music.com. radio2.440music.com is the server name of the server Im trying to install Ubuntu Bionic Beaver 18.04.2. Ubuntu seems to be the only stable OS that will run Mixxx, I sure wish SAMSBroadcast would work on Linux OSs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CasperVersion: 1.394 Date: Mon Mar 25 16:09:05 2019 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.12 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821642 Title: stalls during install or reports an error that the CD might be currupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1821642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713615] Re: ttf-mscorefonts-installer fails because Redirection from https to http is forbidden
I think it would help of somebody created an SRU, https://wiki.ubuntu.com/StableReleaseUpdates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713615 Title: ttf-mscorefonts-installer fails because Redirection from https to http is forbidden To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msttcorefonts/+bug/1713615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1813354] Re: release-upgrader unable to deal with sources.list entries of "deb mirror://"
Most appear in places like Ask Ubuntu (and other Stack Exchange sites). I had not seen "official" information but I searched and found a blueprint: https://blueprints.launchpad.net/ubuntu/+spec/deploy-dynamic-mirrors -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813354 Title: release-upgrader unable to deal with sources.list entries of "deb mirror://" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1813354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815662] Re: upgrade failed looking for ubuntu-minimal -- using mirrors.ubuntu.com in sources
*** This bug is a duplicate of bug 1813354 *** https://bugs.launchpad.net/bugs/1813354 never mind; I was wrong about the URLs -- they were mirror:// so confirming this is a duplicate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815662 Title: upgrade failed looking for ubuntu-minimal -- using mirrors.ubuntu.com in sources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1815662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815662] Re: upgrade failed looking for ubuntu-minimal -- using mirrors.ubuntu.com in sources
*** This bug is a duplicate of bug 1813354 *** https://bugs.launchpad.net/bugs/1813354 also I believe I did not use mirror:// urls but I used the mirror.ubuntu.com urls -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815662 Title: upgrade failed looking for ubuntu-minimal -- using mirrors.ubuntu.com in sources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1815662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815662] Re: upgrade failed looking for ubuntu-minimal -- using mirrors.ubuntu.com in sources
*** This bug is a duplicate of bug 1813354 *** https://bugs.launchpad.net/bugs/1813354 This was marked as a duplicate of bug #1813354 but my situation was different. The upgrader began the upgrade and failed due to a package problem. I only INFERRED that the problem was due to the mirror lines -- it did not report an error with the sources. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815662 Title: upgrade failed looking for ubuntu-minimal -- using mirrors.ubuntu.com in sources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1815662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815662] Re: upgrade failed looking for ubuntu-minimal -- using mirrors.ubuntu.com in sources
I switched the software sources to us.archive.ubuntu.com and it seems to be proceeding with the upgrade from 18.04 to 18.10 just fine now. SO if the release-upgrader cannot reliably upgrade when mirrors.ubuntu.com is in sources.list, maybe it can check for that and suggest a change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815662 Title: upgrade failed looking for ubuntu-minimal -- using mirrors.ubuntu.com in sources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1815662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815662] [NEW] upgrade failed looking for ubuntu-minimal -- using mirrors.ubuntu.com in sources
Public bug reported: I tried to do an upgrade and it looked like it was starting well, but then it complained about the missing ubuntu-minimal package. From looking at the suggested similar errors just now I suspect it's due to using mirrors.ubuntu.com for my packages Months ago I switched to mirrors.ubuntu.com on this netbook because for whatever reason it seems to get really slow updating using any of the regular sources I have tried. For some reason it works much faster using mirrors. On the downside, I have noted a couple of difficulties attempting to pull updates from mirrors over the months, and this is probably one of them. I presume it comes down to packages not being fully distributed when the updates occur, or maybe some other glitch with the mirrors logic. I'm going ahead and noting this in case it's helpful to someone. I'm going to try the upgrade again with an "ordinary" sources.list and if I think to I'll update this bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.30 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CrashDB: ubuntu Date: Tue Feb 12 13:15:04 2019 InstallationDate: Installed on 2018-08-14 (182 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2019-02-12 (0 days ago) VarLogDistupgradeAptlog: Log time: 2019-02-12 12:45:55.807717 Log time: 2019-02-12 12:46:29.637440 Log time: 2019-02-12 12:49:54.070405 Log time: 2019-02-12 13:15:15.008205 VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2019-02-12T12:37:09.175187 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815662 Title: upgrade failed looking for ubuntu-minimal -- using mirrors.ubuntu.com in sources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1815662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803601] Re: motd-news.service scheduled even when /etc/update-motd.d/50-motd-news is not executable
I have the same problem and it looks like this issue brings my server in real trouble. I deactivated this services completly now and hope it helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803601 Title: motd-news.service scheduled even when /etc/update-motd.d/50-motd-news is not executable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1803601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618424] Re: The internet applet crashes randomly.
Fix released in #1619354 ** Changed in: network-manager-applet (Ubuntu) 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/1618424 Title: The internet applet crashes randomly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1618424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806806] Re: package amavisd-new 1:2.11.0-1ubuntu1.1 failed to install/upgrade: installed amavisd-new package post-installation script subprocess returned error exit status 1
Jeg forstår ikke ENGLSK. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806806 Title: package amavisd-new 1:2.11.0-1ubuntu1.1 failed to install/upgrade: installed amavisd-new package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1806806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790360] Re: [wayland] Fullscreen games offset after switching back to them from an app in the same workspace
*** This bug is a duplicate of bug 1732245 *** https://bugs.launchpad.net/bugs/1732245 ** This bug has been marked a duplicate of bug 1732245 [wayland] Fullscreen games offset after returning from alt-tab -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790360 Title: [wayland] Fullscreen games offset after switching back to them from an app in the same workspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1790360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769330] Re: 18.04 regression: liberation text highlight is too small in web browsers.
I just found the bug in Ubuntu. Maybe this is a duplicate of bug #1769654 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769330 Title: 18.04 regression: liberation text highlight is too small in web browsers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-liberation/+bug/1769330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769330] Re: 18.04 regression: liberation text highlight is too small in web browsers.
This may be due to this fonts-liberation bug, first noted in LibreOffice, and fixed in Debian https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=898116 SO maybe someone can apply for a Stable Release Update and get this into Bionic (please?) ** Bug watch added: Debian Bug tracker #898116 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898116 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769330 Title: 18.04 regression: liberation text highlight is too small in web browsers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-liberation/+bug/1769330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769848] Re: wodim no longer works from non-root accounts
I was running into this same issue while trying to copy a CD in K3B (in Pop!_OS 18.04 LTS). Thank you for the tip about commenting out CDR_FIFOSIZE, @zaitseff; I'm now unblocked. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769848 Title: wodim no longer works from non-root accounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cdrkit/+bug/1769848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766217] Re: software updater presents an empty panel for updating
** Attachment added: "AFTER screenshot showing the updates pending" https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1766217/+attachment/5188513/+files/Screenshot%20from%202018-09-13%2012-29-31.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766217 Title: software updater presents an empty panel for updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1766217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766217] Re: software updater presents an empty panel for updating
** Attachment added: "BEFORE image showing the updates missing" https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1766217/+attachment/5188512/+files/Screenshot%20from%202018-09-13%2012-04-18.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766217 Title: software updater presents an empty panel for updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1766217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766217] Re: software updater presents an empty panel for updating
TL;DR -- today using apt-get autoremove deleted the offensive lines in /var/lib/apt/extended_states and restored the list in software-updater -- though I doubt that will work every time. Today I saw the blank software-updater list again on this Xenial (Ubuntu 16.04) system. @eric97's comment caused me to try something OTHER than blow away the file -- I have already installed the latest kernel updates, but apparently didn't get around to removing the outdated ones. Running apt autoremove worked to restore my updates list. I am not sure whether I had lots of old kernels last time, though I doubt it. I no longer use a separate /boot partition on this machine but back when I USED to I got into the habit of running apt autoremove after kernel updates. (Because it a real PITA when your /boot partition fills up.) Session transcript (edited lightly): twt@hostname:~$ sudo apt update [sudo] password for twt: Hit:1 http://security.ubuntu.com/ubuntu xenial-security InRelease Hit:2 http://archive.canonical.com/ubuntu xenial InRelease Hit:3 http://us.archive.ubuntu.com/ubuntu xenial InRelease Hit:4 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease Hit:5 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease Hit:6 http://us.archive.ubuntu.com/ubuntu xenial-security InRelease Reading package lists... Done Building dependency tree Reading state information... Done 16 packages can be upgraded. Run 'apt list --upgradable' to see them. twt@hostname:~$ apt list --upgradeable Listing... Done chromium-browser/xenial-updates,xenial-security,xenial-security 69.0.3497.81-0ubuntu0.16.04.1 amd64 [upgradable from: 68.0.3440.106-0ubuntu0.16.04.1] chromium-browser-l10n/xenial-updates,xenial-updates,xenial-security,xenial-security,xenial-security,xenial-security 69.0.3497.81-0ubuntu0.16.04.1 all [upgradable from: 68.0.3440.106-0ubuntu0.16.04.1] chromium-codecs-ffmpeg-extra/xenial-updates,xenial-security,xenial-security 69.0.3497.81-0ubuntu0.16.04.1 amd64 [upgradable from: 68.0.3440.106-0ubuntu0.16.04.1] firefox/xenial-updates,xenial-security,xenial-security 62.0+build2-0ubuntu0.16.04.4 amd64 [upgradable from: 62.0+build2-0ubuntu0.16.04.3] firefox-locale-en/xenial-updates,xenial-security,xenial-security 62.0+build2-0ubuntu0.16.04.4 amd64 [upgradable from: 62.0+build2-0ubuntu0.16.04.3] initramfs-tools/xenial-updates,xenial-updates 0.122ubuntu8.12 all [upgradable from: 0.122ubuntu8.11] initramfs-tools-bin/xenial-updates 0.122ubuntu8.12 amd64 [upgradable from: 0.122ubuntu8.11] initramfs-tools-core/xenial-updates,xenial-updates 0.122ubuntu8.12 all [upgradable from: 0.122ubuntu8.11] libgit2-24/xenial-updates,xenial-security,xenial-security 0.24.1-2ubuntu0.2 amd64 [upgradable from: 0.24.1-2] libpam-systemd/xenial-updates 229-4ubuntu21.4 amd64 [upgradable from: 229-4ubuntu21.2] libsystemd0/xenial-updates 229-4ubuntu21.4 amd64 [upgradable from: 229-4ubuntu21.2] libudev1/xenial-updates 229-4ubuntu21.4 amd64 [upgradable from: 229-4ubuntu21.2] systemd/xenial-updates 229-4ubuntu21.4 amd64 [upgradable from: 229-4ubuntu21.2] systemd-sysv/xenial-updates 229-4ubuntu21.4 amd64 [upgradable from: 229-4ubuntu21.2] udev/xenial-updates 229-4ubuntu21.4 amd64 [upgradable from: 229-4ubuntu21.2] twt@hostname:~$ uname -a Linux hostname 4.4.0-135-generic #161-Ubuntu SMP Mon Aug 27 10:45:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux twt@hostname:~$ cat /var/lib/apt/extended_states Package: linux-headers-4.4.0-133 Architecture: amd64 Auto-Installed: 1 Package: linux-image-extra-4.4.0-133-generic Architecture: amd64 Auto-Installed: 1 Package: linux-headers-4.4.0-133-generic Architecture: amd64 Auto-Installed: 1 Package: linux-image-4.4.0-133-generic Architecture: amd64 Auto-Installed: 1 Package: linux-headers-4.4.0-134 Architecture: amd64 Auto-Installed: 1 Package: linux-image-extra-4.4.0-134-generic Architecture: amd64 Auto-Installed: 1 Package: linux-headers-4.4.0-134-generic Architecture: amd64 Auto-Installed: 1 Package: linux-image-4.4.0-134-generic Architecture: amd64 Auto-Installed: 1 Package: linux-image-extra-4.4.0-135-generic Architecture: amd64 Auto-Installed: 1 twt@hostname:~$ sudo apt autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-4.4.0-133 linux-headers-4.4.0-133-generic linux-image-4.4.0-133-generic linux-image-extra-4.4.0-133-generic 0 upgraded, 0 newly installed, 4 to remove and 16 not upgraded. After this operation, 303 MB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 384921 files and directories currently installed.) Removing linux-headers-4.4.0-133-generic (4.4.0-133.159) ... Removing linux-headers-4.4.0-133 (4.4.0-133.159) ... Removing linux-image-extra-4.4.0-133-generic (4.4.0-133.159) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-133-generic
[Bug 1766217] Re: software updater presents an empty panel for updating
I have been seeing this.
TL;DR: workaround: delete /var/lib/apt/extended_states
INVESTIGATION
I tried reinstalling the update-manager
$ sudo apt install --reinstall update-manager
but that didn't help.
SO I moved the apt directory and created a blank one
$ sudo mv /var/lib/apt /var/lib/apt.orig
$ sudo mkdir /var/lib/apt
then I updated apt
$ sudo apt update
Get:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease [247 kB]
Get:3 http://archive.canonical.com/ubuntu xenial InRelease [11.5 kB]
...
Get:119 http://us.archive.ubuntu.com/ubuntu xenial-security/multiverse amd64
DEP-11 Metadata [212 B]
Get:120 http://us.archive.ubuntu.com/ubuntu xenial-security/multiverse DEP-11
64x64 Icons [29 B]
Fetched 55.2 MB in 1min 13s (748 kB/s)
AppStream cache update completed, but some metadata was ignored due to errors.
Reading package lists... Done
Building dependency tree... Done
20 packages can be upgraded. Run 'apt list --upgradable' to see them.
$
Now despite the complaint above ("AppStream cache update completed, but some
metadata was ignored due to errors.") software-updater works; it lists the
upgradeable packages.
The only subdirectory that got recreated under /var/lib/apt is
/var/lib/apt/lists (and its subdirectory)
SO I blew away the directory and copied everything except the lists directory
and updated again
$ sudo rm -R /var/lib/apt
$ sudo cp -R /var/lib/apt.orig /var/lib/apt
$ sudo rm -R /var/lib/apt/lists/
$ sudo apt update
Get:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease [247 kB]
Get:3 http://security.ubuntu.com/ubuntu xenial-security InRelease [107 kB]
...
Get:120 http://us.archive.ubuntu.com/ubuntu xenial-security/multiverse DEP-11
64x64 Icons [29 B]
Fetched 55.2 MB in 1min 13s (747 kB/s)
AppStream cache update completed, but some metadata was ignored due to errors.
Reading package lists... Done
Building dependency tree
Reading state information... Done
20 packages can be upgraded. Run 'apt list --upgradable' to see them.
$
I got the same error, HOWEVER Software Updater is blank again.
I tried deleting the /var/lib/apt/periodic directory and updating
$ sudo rm -R /var/lib/apt/periodic/
$ sudo mkdir /var/lib/apt/periodic
$ sudo apt update
Hit:1 http://archive.canonical.com/ubuntu xenial InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Hit:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit:4 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease
Hit:6 http://us.archive.ubuntu.com/ubuntu xenial-security InRelease
Hit:7 http://security.ubuntu.com/ubuntu xenial-security InRelease
Hit:5 http://screenshots.getdeb.net xenial-getdeb InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
20 packages can be upgraded. Run 'apt list --upgradable' to see them.
$ ls /var/lib/apt/periodic
update-success-stamp
$
Now I no longer see a metadata error from apt, but software-updater is
still blank.
SO I delete the extended_states file
$ sudo rm /var/lib/apt/extended_states
$ sudo apt update
Hit:1 http://archive.canonical.com/ubuntu xenial InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Hit:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit:4 http://security.ubuntu.com/ubuntu xenial-security InRelease
Hit:5 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease
Hit:6 http://us.archive.ubuntu.com/ubuntu xenial-security InRelease
Hit:7 http://screenshots.getdeb.net xenial-getdeb InRelease
Reading package lists... Done
Building dependency tree... Done
20 packages can be upgraded. Run 'apt list --upgradable' to see them.
$
NOW software-updater is showing the upgradeable files
SO just to be sure, I copied the original stuff back and deleted JUST the
extended_states file
$ sudo rm -R /var/lib/apt/
$ sudo cp -R /var/lib/apt.orig/ /var/lib/apt/
$ sudo rm /var/lib/apt/extended_states
$
AND software_updater is now showing the upgradeable packages. There's the
workaround. Are there consequences of having no extended_states file?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766217
Title:
software updater presents an empty panel for updating
To manage notifications about this bug go to:
[Bug 1780323] [NEW] boot from usb freezes
Public bug reported: When i try to boot a HP laptop, 15-CB011NO, from a USB stick with Ubuntu 18.04 it boots and shows directly the desktop, but then I can not take any further actions. The mouse moves the cursor but nothing happens when I click. I have followed the recommendations what to change in the EFI. Here is what the USB stick contains ~$ ll /media/tpollak/UBUNTU\ 18_0/ total 196 drwxr-xr-x 13 tpollak tpollak 8192 jan 1 1970 ./ drwxr-x---+ 3 rootroot 4096 jul 5 22:19 ../ -rw-r--r-- 1 tpollak tpollak 34494 jun 8 21:25 autorun.ico -rw-r--r-- 1 tpollak tpollak 230 jun 8 21:25 autorun.inf drwxr-xr-x 3 tpollak tpollak 8192 jun 8 21:19 boot/ drwxr-xr-x 2 tpollak tpollak 8192 jun 8 21:19 casper/ drwxr-xr-x 2 tpollak tpollak 8192 jun 8 21:19 .disk/ drwxr-xr-x 3 tpollak tpollak 8192 jun 8 21:24 dists/ drwxr-xr-x 3 tpollak tpollak 8192 jun 8 21:24 EFI/ drwxr-xr-x 2 tpollak tpollak 8192 jun 8 21:24 install/ drwxr-xr-x 2 tpollak tpollak 16384 jun 8 21:24 isolinux/ -rw-r--r-- 1 tpollak tpollak 24055 jun 8 21:24 md5sum.txt drwxr-xr-x 2 tpollak tpollak 8192 jun 8 21:24 pics/ drwxr-xr-x 4 tpollak tpollak 8192 jun 8 21:24 pool/ drwxr-xr-x 2 tpollak tpollak 8192 jun 8 21:25 preseed/ -rw-r--r-- 1 tpollak tpollak 231 jun 8 21:25 README.diskdefines -rw-r--r-- 1 tpollak tpollak94 jun 8 21:25 syslinux.cfg drwxr-xr-x 2 tpollak tpollak 8192 jun 8 21:19 'System Volume Information'/ -rw-r--r-- 1 tpollak tpollak 0 jun 8 21:25 ubuntu ~$ ** Affects: openssl (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/1780323 Title: boot from usb freezes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1780323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780319] [NEW] openssl des3 decryption fails in 18.04
Public bug reported: Since I upgraded to Ubuntu 18.04 I get ~$ openssl des3 -d /tmp/loesenord.htm enter des-ede3-cbc decryption password: bad decrypt 140555004862912:error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt:../crypto/evp/evp_enc.c:536: The encryption was done with Ubuntu 17.10. And the decryption worked well in 17.10. Encryption/decryption in Ubuntu 18.04 works well. ~$ lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 ~$ apt-cache policy openssl openssl: Installed: 1.1.0g-2ubuntu4.1 Candidate: 1.1.0g-2ubuntu4.1 Version table: *** 1.1.0g-2ubuntu4.1 500 500 http://se.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 1.1.0g-2ubuntu4 500 500 http://se.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Affects: openssl (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/1780319 Title: openssl des3 decryption fails in 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1780319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736222] Re: speech-dispatcher distorts all sound
My comment above about extra processes is described in Bug #1496542 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736222 Title: speech-dispatcher distorts all sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1736222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736222] Re: speech-dispatcher distorts all sound
Workaround: when I hear the distorted sound, I open a terminal and issue this command $ killall speech-dispatcher This works until the next time I hit a web site that causes the issue. I don't know anything about speech dispatcher, but I wonder if multiple speech-dispatcher processes be interfering with each other? I usually start with $ ps uax | grep speech and I usually see five or six processes twt@host:~$ ps uax | grep speech twt 9165 0.0 0.0 289000 5092 ?Sl 11:01 0:00 /usr/lib/speech-dispatcher-modules/sd_dummy /etc/speech-dispatcher/modules/dummy.conf twt 9168 0.0 0.0 289012 4976 ?Sl 11:01 0:00 /usr/lib/speech-dispatcher-modules/sd_generic /etc/speech-dispatcher/modules/generic.conf twt 9171 0.0 0.0 289000 5088 ?Sl 11:01 0:00 /usr/lib/speech-dispatcher-modules/sd_cicero /etc/speech-dispatcher/modules/cicero.conf twt 9176 0.0 0.0 327320 8756 ?Sl 11:01 0:00 /usr/lib/speech-dispatcher-modules/sd_espeak /etc/speech-dispatcher/modules/espeak.conf twt 9181 0.0 0.0 97216 2220 ?Ssl 11:01 0:00 /usr/bin/speech-dispatcher --spawn --communication-method unix_socket --socket-path /run/user/1000/speech-dispatcher/speechd.sock -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736222 Title: speech-dispatcher distorts all sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1736222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 951692] Re: Evolution Connection reset by peer when checking mail yahoo.com
Reply to gf: Yes I can confirm that this issue is not any longer a concern; you can close the ticket. Thank you so much! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/951692 Title: Evolution Connection reset by peer when checking mail yahoo.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/951692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768852] Re: Kernel bug when unplugging Thunderbolt 3 cable, leaves xHCI host controller dead
I can also confirm that his fixes the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768852 Title: Kernel bug when unplugging Thunderbolt 3 cable, leaves xHCI host controller dead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1738412] Re: Init script fails test on reload/restart because of faulty regex
On 2018-01-02 15:38, Robie Basak wrote: > Tommy, thank you for bringing our attention to this. > > It looks like this issue *is* fixed in the current stable Ubuntu > release. Perhaps you were looking at the changelog against a newer > release of Ubuntu than the one you are using? >> This is a very serious issue... > Why is this "a very serious issue"? It seems to me that it only affects > invalid configurations so should only affect development and testing of > deployments rather than in production? The workaround (if it can be > called that) is to fix the invalid configuration. I kind of hope that this is a joke :) You know sometimes things don't go as intended, that's why the check is there. > The fix does look reasonable to SRU though. I wonder if > https://anonscm.debian.org/cgit/pkg-squid/pkg- > squid.git/commit/?id=6ac65f75a971a4a is also relevant? That may be a > separate bug though, or we may need an additional test case for it. So it has been a while now. What's the next step to get this in? The fix is really trivial. Can I help with something to get it rolling? -- TN -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738412 Title: Init script fails test on reload/restart because of faulty regex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1738412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749831] Re: Update failed due to problem with ubuntu-desktop
started using a terminal and it looks like it's going to finish twt@Dimension1:~$ sudo apt update [sudo] password for twt: Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB] Hit:2 http://archive.canonical.com/ubuntu xenial InRelease Hit:3 http://screenshots.getdeb.net xenial-getdeb InRelease Get:4 http://security.ubuntu.com/ubuntu xenial-security/main amd64 DEP-11 Metadata [67.4 kB] Hit:5 http://us.archive.ubuntu.com/ubuntu xenial InRelease Get:6 http://security.ubuntu.com/ubuntu xenial-security/main DEP-11 64x64 Icons [66.9 kB] Get:7 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 DEP-11 Metadata [51.3 kB] Get:8 http://security.ubuntu.com/ubuntu xenial-security/universe DEP-11 64x64 Icons [80.2 kB] Get:9 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB] Get:10 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB] Get:11 http://us.archive.ubuntu.com/ubuntu xenial-security InRelease [102 kB] Get:12 http://us.archive.ubuntu.com/ubuntu xenial-updates/main Sources [296 kB] Get:13 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [724 kB] Get:14 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages [674 kB] Get:15 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 DEP-11 Metadata [317 kB] Get:16 http://us.archive.ubuntu.com/ubuntu xenial-updates/main DEP-11 64x64 Icons [217 kB] Get:17 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [588 kB] Get:18 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe i386 Packages [545 kB] Get:19 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 DEP-11 Metadata [190 kB] Get:20 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe DEP-11 64x64 Icons [272 kB] Get:21 http://us.archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 DEP-11 Metadata [5,888 B] Get:22 http://us.archive.ubuntu.com/ubuntu xenial-security/main amd64 DEP-11 Metadata [67.4 kB] Get:23 http://us.archive.ubuntu.com/ubuntu xenial-security/main DEP-11 64x64 Icons [66.9 kB] Get:24 http://us.archive.ubuntu.com/ubuntu xenial-security/universe amd64 DEP-11 Metadata [51.3 kB] Get:25 http://us.archive.ubuntu.com/ubuntu xenial-security/universe DEP-11 64x64 Icons [80.2 kB] Fetched 4,768 kB in 7s (651 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 37 packages can be upgraded. Run 'apt list --upgradable' to see them. twt@Dimension1:~$ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: compiz compiz-core compiz-gnome compiz-plugins-default libcompizconfig0 libdecoration0 The following packages will be upgraded: apt apt-transport-https apt-utils bsdutils gnome-disk-utility libapt-inst2.0 libapt-pkg5.0 libblkid1 libegl1-mesa libfdisk1 libgbm1 libgl1-mesa-dev libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libgles2-mesa libmount1 libsmartcols1 libunity-control-center1 libuuid1 libwayland-egl1-mesa libxatracker2 linux-firmware mesa-common-dev mesa-vdpau-drivers mount resolvconf unity-control-center unity-control-center-faces util-linux uuid-runtime 31 upgraded, 0 newly installed, 0 to remove and 6 not upgraded. Need to get 56.6 MB/59.8 MB of archives. After this operation, 21.5 kB disk space will be freed. Do you want to continue? [Y/n] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749831 Title: Update failed due to problem with ubuntu-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1749831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749831] Re: Update failed due to problem with ubuntu-desktop
twt@Dimension1:~$ sudo apt full-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following package was automatically installed and is no longer required: session-shortcuts Use 'sudo apt autoremove' to remove it. The following packages will be REMOVED: ubuntu-desktop unity unity-tweak-tool The following packages will be upgraded: compiz compiz-core compiz-gnome compiz-plugins-default libcompizconfig0 libdecoration0 6 upgraded, 0 newly installed, 3 to remove and 0 not upgraded. Need to get 1,469 kB of archives. After this operation, 9,604 kB disk space will be freed. Do you want to continue? [Y/n] n Abort. twt@Dimension1:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749831 Title: Update failed due to problem with ubuntu-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1749831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749831] Re: Update failed due to problem with ubuntu-desktop
I am assuming there's no good reason my system is telling me to ditch Unity so I'm holding off for now -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749831 Title: Update failed due to problem with ubuntu-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1749831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
