[Bug 2080039] Re: Kernel BUG: Bad page state in process kswapd0
I am seeing this with linux-image-6.8.0-40-generic version 6.8.0-40.40~22.04.3 on a Dell PowerEdge R750xa with 384G of ECC RAM running BTRFS for all storage. It crashes like this every day or two with that kernel but on linux- image-6.5.0-28-generic version 6.5.0-28.29~22.04.1 it is solid and has never crashed. I think it's the same issue as this. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056706 Also this bug might be the same issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080039 Title: Kernel BUG: Bad page state in process kswapd0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056706] Re: System unstable, kernel ring buffer flooded with "BUG: Bad page state in process swapper/0"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080039 I just saw this bug about BTRFS. My system in question is running BTRFS for root and has no swap. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056706 Title: System unstable, kernel ring buffer flooded with "BUG: Bad page state in process swapper/0" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056706] Re: System unstable, kernel ring buffer flooded with "BUG: Bad page state in process swapper/0"
I am seeing this with linux-image-6.8.0-40-generic version 6.8.0-40.40~22.04.3 on a Dell PowerEdge R750xa with 384G of ECC RAM. It crashes like this every day or two with that kernel but on linux- image-6.5.0-28-generic version 6.5.0-28.29~22.04.1 it is solid and has never crashed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056706 Title: System unstable, kernel ring buffer flooded with "BUG: Bad page state in process swapper/0" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1978310] Re: Installing fuse package removes other important packages which causes instabilities
I got this bug after installing fuse libfuse2 To get the file manager back, I used: sudo apt install ubuntu-desktop To find recently removed packages, use: grep "remove " /var/log/dpkg.log Good luck. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1978310 Title: Installing fuse package removes other important packages which causes instabilities To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse/+bug/1978310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063110] Re: rtorrent crashes on startup
Seconded. Doing an "apt source rtorrent", applying this patch, building and installing fixes the issue for me. Rakshasa hasn't done an official release since 2019, and this commit has been sitting in trunk for over a year. It would be nice to see this patch expedited. I can't tell how long we'll be waiting for the next upstream release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063110 Title: rtorrent crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtorrent/+bug/2063110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063151] [NEW] cannot upgrade python3-wheel with pip
Public bug reported:
Leveraging `PIP_BREAK_SYSTEM_PACKAGES`, I expect to be able to install
the latest version of wheel.
```
docker run --rm -it ubuntu:noble bash -c 'apt update;
DEBIAN_FRONTEND=noninteractive apt install -y python3-pip;
PIP_BREAK_SYSTEM_PACKAGES=1 pip install -U wheel'
```
Instead this errors with:
```
Requirement already satisfied: wheel in /usr/lib/python3/dist-packages (0.42.0)
Collecting wheel
Downloading wheel-0.43.0-py3-none-any.whl.metadata (2.2 kB)
Downloading wheel-0.43.0-py3-none-any.whl (65 kB)
65.8/65.8 kB 1.4 MB/s eta 0:00:00
Installing collected packages: wheel
Attempting uninstall: wheel
Found existing installation: wheel 0.42.0
ERROR: Cannot uninstall wheel 0.42.0, RECORD file not found. Hint: The package
was installed by debian.
```
```
root@2a030f2b7070:/# lsb_release -rd
No LSB modules are available.
Description:Ubuntu Noble Numbat (development branch)
Release:24.04
```
```
root@2a030f2b7070:/# apt-cache policy python3-wheel
python3-wheel:
Installed: (none)
Candidate: 0.42.0-2
Version table:
0.42.0-2 500
500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages
```
** Affects: wheel (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/2063151
Title:
cannot upgrade python3-wheel with pip
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wheel/+bug/2063151/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062446] [NEW] 50+ minutes CPU time for /tmp/ubuntu-release-upgrader-29r0z57l/mantic is excessive
Public bug reported: USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 11954 51.0 1.2 555772 196136 pts/2 Rl+ 10:15 50:39 /usr/bin/python3 -s /tmp/ubuntu-release-upgrader-29r0z57l/mantic --mode=server --frontend=DistUpgradeViewText This amount of CPU time on a i7-8665U is grossly excessive. According to Passmark the latest i9 CPUs are only about 2.5* faster than this one which means it would take 20+ minutes on an i9. At least there should be an option for the user to skip this step. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.14 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CrashReports: 640:246836501:124:1780063:2024-04-19 10:21:42.539683522 +1000:2024-04-19 10:21:42.547683513 +1000:/var/crash/_usr_libexec_tracker-extract-3.246836501.crash CurrentDesktop: KDE Date: Fri Apr 19 11:39:48 2024 InstallationDate: Installed on 2023-04-14 (371 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to mantic on 2024-04-19 (0 days ago) VarLogDistupgradeApttermlog: Error: [Errno 13] Permission denied: '/var/log/dist-upgrade/apt-term.log' ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062446 Title: 50+ minutes CPU time for /tmp/ubuntu-release-upgrader-29r0z57l/mantic is excessive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2062446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055310] Re: dmesg spammed by virtui-fs and 9pnet-virtio messages
Is this related to https://bugs.launchpad.net/ubuntu/+source/lxd-agent- loader/+bug/2054814 ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055310 Title: dmesg spammed by virtui-fs and 9pnet-virtio messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976524] [NEW] Please sync liblivemedia from debian for jammy
Public bug reported: liblivemedia is available on focal, but not jammy, could it be sync'd from debian? ** Affects: liblivemedia (Ubuntu) Importance: Undecided Status: New ** Tags: needs-packaging ** Summary changed: - Please sync liblivemedia from debian bullseye for jammy + Please sync liblivemedia from debian for jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976524 Title: Please sync liblivemedia from debian for jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liblivemedia/+bug/1976524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971743] [NEW] llvm is not built with curl support
Public bug reported: As of LLVM 14, it can be built with -DLLVM_ENABLE_CURL=ON, which enables the debuginfod client in llvm-symbolizer, which would be an awesome thing to have. It's clear that it's not turned on: $ llvm-debuginfod-find-14 --executable=1 5d016364c1cb69dd No working HTTP client is available. ** Affects: llvm-defaults (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/1971743 Title: llvm is not built with curl support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-defaults/+bug/1971743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963976] Re: Installing nvidia-cuda-toolkit removes nvidia-driver-510
Hi, The same issue here - it wants to force me back to nvidia-driver-470. Is there a way around this? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963976 Title: Installing nvidia-cuda-toolkit removes nvidia-driver-510 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-cuda-toolkit/+bug/1963976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946529] [NEW] Logitech Q9000 default mic gain too high, causes distortion
Public bug reported:
The file /var/lib/alsa/asound.state has the following part for the
settings for the Logitech Q9000 camera.
control.3 { iface MIXER name 'Mic Capture Volume' value 0 comment {
access 'read write' type INTEGER count 1 range '0 - 3072' dbmin 1800
dbmax 3000 dbvalue.0 1800 } }
The dbmin value of 1800 (18db) is too high and causes the mic signal to
be distorted. The value should probably be 0 and the default value
(dbvalue.0 1800) should also probably be set to 0 (0db) and not 1800
(18 db.)
With the dbmin of 1800, it is impossible to set this any lower than 18db
in alsamixer.
In my system, this value comes from /proc/asound/card1/usbmixer and is
linked to /proc/asound/Q9000/usbmixer.
I've tested this out by editing /var/lib/alsa/asound.state to set dbmin
and dbvalue.0 to 0 and the sound on the microphone stops being
distorted.
Description:Ubuntu 21.04
Release:21.04
I have not idea what the package is, but I listed the files so hopefully
that is good enough.
What I expect to happen:
To have the default value for the mic gain to not default so high as to cause
distortion and the the value to be able to be set to 0db (or less even?) in
alsamixer.
What mappened instead?
The mic distorts because the lowest available gain is 18db. You can't set this
below 18db in alsa mixer. This happens in any program that uses the mic input.
** Affects: kubuntu-settings (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/1946529
Title:
Logitech Q9000 default mic gain too high, causes distortion
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1946529/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879370] Re: Ubuntu dock glitches in auto-hide during setting
Possible duplicate of https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1881941 ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879370 Title: Ubuntu dock glitches in auto-hide during setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1879370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881941] Re: Ubuntu dock behaves crazy when hidden at the bottom of the screen
I switched to Wayland today because of a different issue concerning X-11 crashing while using display ports and as a side effect do not see this issue at all now. I suspect that one of the following to be true: 1. the issue was fixed in another bug 2. Using Wayland instead of X11 is a work around to this issue. As the issue relates to the interaction between Gnome and X11. Can someone confirm to me that this issue still exists and whether or not switching to Wayland instead of X11 works around the issue? Just because it worked for me, doesn't mean that it's a fix for everyone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881941 Title: Ubuntu dock behaves crazy when hidden at the bottom of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1881941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756840] Re: Buggy, under-maintained, not fit for main anymore; alternatives exist
I just installed Ubuntu 20.04 on a new machine and I’m a little frustrated that the installer made no mention of encrypting my home directory, which is what I was planning to do. I did a search and found out this is why. If ecryptfs is so broken and better alternatives exist, why does the installer not support any of them? Do I need to file a bug with the installer? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756840 Title: Buggy, under-maintained, not fit for main anymore; alternatives exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1756840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881941] Re: Ubuntu dock behaves crazy when hidden at the bottom of the screen
I can recreate this issue with many other applications, not limited to intellij. From my experience, this has much more to do with timing. Order of operations for recreation that I tested with only firefox open: 1. Make any program doc/stick to the bottom of the screen (easiest way to do this is to make the program full screen). 2. Move your mouse cursor to the bottom of the screen to unhide the bottom dock. (This will force it to draw over the full screen aplication you have open). 3. Very quickly move your cursor away from the bottom of the screen forcing the dock to start to hide again. 4. Before the doc hides again, this happens very quickly, move the mouse back down to the bottom of the screen to unhide the dock again. Very often, but not always, this procedure will recreate the bug and cause the dock menu to fidgit between trying to hide its self and un- hide its self. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881941 Title: Ubuntu dock behaves crazy when hidden at the bottom of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1881941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922783] [NEW] 21.04 kubuntu strange first screen on boot from iso
Public bug reported: When booting from an iso (kubuntu 21.04) the first screen of the installer is on a timer, goes away and you can't get back to it. All it says is "You may wish to read the release notes or update this installer." See attached screen shot. This was reproduce on hardware and in 2 VMs. Release: 21.04 Description: Unbuntu Hirsute Hippo (development branch) Package Version: NA What I expected: Boot from iso and see the screen with the 2 buttons that say try or install. What happened instead: Booted from iso. Saw a screen on a timer that went away on its own and I couldn't get back to it. All it says is "You may wish to read the release notes or update this installer." ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Attachment added: "kubuntuOpen.png" https://bugs.launchpad.net/bugs/1922783/+attachment/5484867/+files/kubuntuOpen.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922783 Title: 21.04 kubuntu strange first screen on boot from iso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1922783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881941] Re: Ubuntu dock behaves crazy when hidden at the bottom of the screen
I'm a capable software developer. However, I am at a loss on where to start debugging this issue. Does anyone have any idea of where to start? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881941 Title: Ubuntu dock behaves crazy when hidden at the bottom of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1881941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906155] Re: USB Passthrough Fails on Start, Needs domain Reset
I really wish I could pinpoint the exact root cause, to be able to feed it back, help others (i.e. fix it once and for all, for everyone :-)). So far though, no luck. I'm still digging, I haven't given up! Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906155 Title: USB Passthrough Fails on Start, Needs domain Reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906155] Re: USB Passthrough Fails on Start, Needs domain Reset
FYI, several updates here - for other reasons, but ... BIOS, Linux (Ubuntu), qemu (to master) => now it works on boot. Arrgh! I only say that because I can't duplicate it any more, with all these updates. That's good overall. LOL! Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906155 Title: USB Passthrough Fails on Start, Needs domain Reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906155] Re: USB Passthrough Fails on Start, Needs domain Reset
Sure, will do. Just to make sure, this mailing list I assume? https://lists.nongnu.org/mailman/listinfo/qemu-devel Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906155 Title: USB Passthrough Fails on Start, Needs domain Reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906155] Re: USB Passthrough Fails on Start, Needs domain Reset
Yep, checked the devices (thanks!), and I get, $ lsusb -v -d 046d:c52b | grep bInterfaceProtocol bInterfaceProtocol 1 Keyboard bInterfaceProtocol 2 Mouse bInterfaceProtocol 0 Pretty much as expected. Hmm, not sure what else to do - or is it just ... live with it? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906155 Title: USB Passthrough Fails on Start, Needs domain Reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906155] Re: USB Passthrough Fails on Start, Needs domain Reset
OK, this is going to sound crazy, but ... I did exactly like you note above - and the same thing happens. My USB device isn't seen / avaiable on start, but after I reset the VM .. voila! It's there and works. OK, wondering what else it could be. I have a USB hub where the device is plugged in - will try removing that (variable) ... nope, that's not it either. Arrgh!?!? LOL. This really is very odd. I'm open to any thoughts you have. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906155 Title: USB Passthrough Fails on Start, Needs domain Reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906155] Re: USB Passthrough Fails on Start, Needs domain Reset
BTW, one other interesting thing I just noticed, in lsusb. As this Logitech receiver connects to multiple devices (e.g. keyboard, mouse), I see it "3 times", /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 8, If 2, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 1: Dev 8, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 1: Dev 8, If 1, Class=Human Interface Device, Driver=usbhid, 12M Could that be part of the fun here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906155 Title: USB Passthrough Fails on Start, Needs domain Reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906155] Re: USB Passthrough Fails on Start, Needs domain Reset
OK, sort of figured it out :-). Seems I need to also modify /etc/apparmor.d/usr.sbin.libvirtd. Let me dig into that one separately ... LOL. On the USB front, thinking a basic configuration file should be sufficient for debugging - no drives needed, etc. Do you happen to have one (or a partial) that you can share - so I can try the setup you have? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906155 Title: USB Passthrough Fails on Start, Needs domain Reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906155] Re: USB Passthrough Fails on Start, Needs domain Reset
OK, tried other USB controllers (piix4, vt82c686b), same issue - this is really odd! Thought I'd update to the latest / official v5.2.0 qemu, but now I get this when trying to run it. Huh?!?! error: internal error: Failed to start QEMU binary /usr/local/bin/qemu-system-x86_64 for probing: libvirt: error : cannot execute binary /usr/local/bin/qemu-system-x86_64: Permission denied No changes to my apparmor file - checked :-). Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906155 Title: USB Passthrough Fails on Start, Needs domain Reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906155] Re: USB Passthrough Fails on Start, Needs domain Reset
OK, I got to thinking about this other bug I had seen a while back. Initially thought it was not related, but maybe it is after all? https://bugs.launchpad.net/qemu/+bug/1694808 Perhaps we are using different USB controllers, and that's why we see different results? I have the following ... match to your setup? And my USB device, So the USB device is on ich9-uhci2, correct? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906155 Title: USB Passthrough Fails on Start, Needs domain Reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906155] Re: USB Passthrough Fails on Start, Needs domain Reset
> If you tell me how to initialize a mouse there I can try :-) Sorry, bad wording on my part. The USB device I am connecting is a Logitech Nano Receiver ... keyboard and mouse both connected to it. So at the UEFI / Grub stage - only the keyboard, as you correctly point out :-). > It only matters if you have your mouse working, but then issues with > the multitude of mouse-inputs. Not 100% sure I follow you :-). But I do have "two" mice connected - one on the guest (USB Passthrough), the other to virt-manager ... which is running over X-Windows from the host to an X-Server. Not sure that makes any difference, but just in case! > Due to that if you use GPU passthrough (and no other virtual display) > the channel through spice won't exists and therefore no conflicting > inputs will happen. I can disable spice if you want, go only USB Passthrough. Just let me know. I have done that before, can try it (for this particular issue). BTW, another thought. The VM is defined as Q35 - in fact, a few items below, just in case they could be part of this, hvm Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906155 Title: USB Passthrough Fails on Start, Needs domain Reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906155] Re: USB Passthrough Fails on Start, Needs domain Reset
Thanks for the details! I thought we may be on to something, but not quite. I saw a couple deltas in your config (vs. mine), 1) No OVMF_VARS - tried removing this, no difference. 2) You are checking the mouse in the OS - checked that as well (not just UEFI / Ubuntu Grub menu), nope, it's still not there. I can't log in, no keyboard or mouse ... but I think yours is up for the login screen, right? FYI, you note about GPU Passthrough - not sure I'm following you 100%, but I do have a second GPU in the machine, and I enable it for GPU Passthrough. It works fine (actually, very nicely!). Not sure why this matters though? No issue here sharing config details - is there something in particular that would help? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906155 Title: USB Passthrough Fails on Start, Needs domain Reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906155] Re: USB Passthrough Fails on Start, Needs domain Reset
> I've not yet seen/reproduced the same on qemu 5.0/edk2 2020.08-1 :-/ So you don't see this issue, or haven't had a chance to check it? No biggie either way, just trying to understand your comment :-). > Would you mind outlining your case on the upstream mailing list? Yes, no issue at all - but should we wait for you to test? If you see the same issue, NP at all flagging this. But if you don't, then somehow configuration related? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906155 Title: USB Passthrough Fails on Start, Needs domain Reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906155] Re: USB Passthrough Fails on Start, Needs domain Reset
Yep, makes sense ... but I have to admit, I screwed up. Sorry! Complete bonehead on my part. When I tested Ubuntu (guest), I was connected over VNC, so I didn't correctly / properly test the USB interface. So, I re-checked, making sure to use QEMU + UEFI (Tianocore, stock VARS), and check USB. It does exactly the same thing (now :-))! And this makes more sense, it was very odd that the OS would play into it. I also here have to do a reset (of the guest), to get the USB to show up. So it really does seem to be an issue between QEMU and UEFI, agreed? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906155 Title: USB Passthrough Fails on Start, Needs domain Reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906673] Re: Realm join hangs
*** This bug is a duplicate of bug 1906627 *** https://bugs.launchpad.net/bugs/1906627 I have observed this same behaviour with 'adcli join' when using adcli 0.8.2-1-ubuntu1 but adding the --use-ldaps parameter on the command line allowed the join to complete successfully. Without using the --use-ldaps flag, using tcpdump I observed the LDAP operations were happening in the clear on port 389. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906673 Title: Realm join hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1906673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906155] Re: USB Passthrough Fails on Start, Needs domain Reset
Hmmm ... not getting Windows 10 to boot now. Trying to follow https://k3a.me/boot-windows-partition-virtually-kvm-uefi/, set up os in my config (xml), hvm /var/lib/libvirt/qemu/nvram/OVMF_CODE.fd /var/lib/libvirt/qemu/nvram/win8.1_VARS.fd I get to the UEFI menu, but it won't seem to boot to my drive. Thoughts / suggestions? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906155 Title: USB Passthrough Fails on Start, Needs domain Reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906155] Re: USB Passthrough Fails on Start, Needs domain Reset
> This particular rule is (re)loaded on guest start, so stop+start a > guest and it is updated. So no need to restart apparmor? And both entries are required (in the libvirt-qemu file)? > Yeah - kind of, and now the request it to test Ubuntu and Windows > guest with the same OVMF based UEFI. Funny! Only because we're very much on the same page - was already trying to get that going :-). Will let you know! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906155 Title: USB Passthrough Fails on Start, Needs domain Reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906155] Re: USB Passthrough Fails on Start, Needs domain Reset
> Doing the same in /etc/apparmor.d/local/abstractions/libvirt-qemu is > better to now get conflicts on upgrades. Makes sense, thanks! Will move the items there. Both entries are needed? Seems like I can just restart apparmor after (or at least that's working for me). > if the windows guest didn't have that it probably runs on seabios or > some other non UEFI path. Agreed! Looks like it runs SeaBIOS (fast flash of the screen :-)). So the issue seems to be UEFI and QEMU? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906155 Title: USB Passthrough Fails on Start, Needs domain Reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906155] Re: USB Passthrough Fails on Start, Needs domain Reset
No worries, and thanks for all the help so far - it really is appreciated! On the apparmor issue, is this the "right" fix? I modified /etc/apparmor.d/abstractions/libvirt-qemu, adding, /usr/local/bin/qemu-system-x86_64 rmix, /usr/local/share/qemu/** r, Or is there a "better" (correct) way? As for Windows/Linux vs. macOS guests, I don't think they are usign the same UEFI (are they?). I did reboot the Windows guest, and it looks to be a different "BIOS", agreed? Checking the xml configuration files, they are a bit different (macOS copied below, Windows does not include this). So is it (specifically?) UEFI vs. QEMU (i.e. that is the issue)? OVMF_CODE.fd OVMF_VARS.fd I could definitely be wrong here, but thinking that "stock" UEFI should work / be supported? Thanks again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906155 Title: USB Passthrough Fails on Start, Needs domain Reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906155] Re: USB Passthrough Fails on Start, Needs domain Reset
FYI, was able to get the following version of QEMU running (using the info at https://stackoverflow.com/questions/10817813/apparmor-causes-issues-on-libvirt-with-custom-qemu), QEMU emulator version 5.1.93 (v5.2.0-rc3) Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers No delta - still reacts the same. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906155 Title: USB Passthrough Fails on Start, Needs domain Reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906155] Re: USB Passthrough Fails on Start, Needs domain Reset
OK, some interesting findings :-). And back to thinking it may be QEMU related? Let me explain, by all means disagree! 1) I found that using OpenCore with macOS, I no longer need a custom UEFI. So, I tried the UEFI that comes with Ubuntu (apt install ovmf, copied the files over). No change. So then, I cloned and built the latest UEFI from Tianocore / EDK II (https://github.com/tianocore/edk2). Copied that over (and VARS, default), no delta. And as I can't get into the UEFI menu on VM startup (i.e. press ESC, F2, etc.) ... seems to be OS independent, just an issue between UEFI and QEMU - agreed? 2) Figured I'd try to clone, build and run the latest version of QEMU, see if that is it - FYI, the current version in Ubuntu that I'm running is, QEMU emulator version 5.0.0 (Debian 1:5.0-5ubuntu9.2) Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers OK, that said ... I can build, install => but can't get apparmor to let me run my custom QEMU executable (arrgh!). I even tried disabling security_driver (set to "none" in /etc/libvirt/qemu.conf, restarted libvirtd.service) ... but no joy. Can't get the latest QEMU to run. Any thoughts here would be appreciated! This is to see if it's an "older" issue, and may be resolved already. 3) An interesting side note, when I did get into the UEFI menu (post VM reset), changed the resolution ... I could no longer boot (fully) my guest OS. Had to reboot my host OS (Ubuntu), then all OK. Very odd, but an observation :-). Thanks for all the help! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906155 Title: USB Passthrough Fails on Start, Needs domain Reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906155] Re: USB Passthrough Fails on Start, Needs domain Reset
> The one obvious next test would be to shut down the macOS guest and try an ubuntu guest with the same forwards. That will allow us to see if it is "virtualization-components" or actually "guest OS" that we need to think about. Good idea. OK, so I shut down all VM's, added this same USB device to a Windows 10 VM I also had defined (on the same host OS). Started it up (same way, virsh start) => booted up, and ... USB device works! So it seems to be guest OS related, agreed? And actually, not even that I'd say, as I can't even use it in the bootloader / UEFI, so not really even the OS, but the bootloader / UEFI? And that sort of aligns with the watchdog reset, as then it works, but still hasn't gotten to the OS (boot). Agreed? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906155 Title: USB Passthrough Fails on Start, Needs domain Reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906155] Re: USB Passthrough Fails on Start, Needs domain Reset
No issue with reboot, worry about that after we debug this :-). I tried the noted command, but I get, bash: echo: write error: No such device bash: echo: write error: No such device FYI, $ ls -alF /sys/bus/pci/drivers/xhci_hcd/ total 0 drwxr-xr-x 2 root root0 Dec 2 17:51 ./ drwxr-xr-x 35 root root0 Dec 2 17:51 ../ lrwxrwxrwx 1 root root0 Dec 2 17:51 :02:00.0 -> ../../../../devices/pci:00/:00:01.3/:02:00.0/ lrwxrwxrwx 1 root root0 Dec 2 17:51 :0b:00.3 -> ../../../../devices/pci:00/:00:07.1/:0b:00.3/ --w--- 1 root root 4096 Dec 2 17:53 bind lrwxrwxrwx 1 root root0 Dec 2 17:51 module -> ../../../../module/xhci_pci/ --w--- 1 root root 4096 Dec 2 17:51 new_id --w--- 1 root root 4096 Dec 2 17:51 remove_id --w--- 1 root root 4096 Dec 2 17:51 uevent --w--- 1 root root 4096 Dec 2 17:53 unbind So I tried echo -n ":02:00.0", but no recovery. Also, unplug / plug ... nope. So then I tried my old standby :-). virsh reset macOS => Nope, not working now. Had to destroy the VM, then the usual (start, reset) ... working again. Thoughts? Also just stumbled on to this by accident ... on VM start, no USB (as above). But leave it 5 min, and the VM reboots itself (internally, not restart at the virsh "level" ... UEFI watchdog perhaps?). And then USB is OK. So is it some sort of race condition / timing issue at initial VM startup? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906155 Title: USB Passthrough Fails on Start, Needs domain Reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906155] Re: USB Passthrough Fails on Start, Needs domain Reset
OK, let me try to explain what I did here - and yell if this is not clear! Step #1, check lsusb -t before any qemu start, /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 3: Dev 26, If 0, Class=Human Interface Device, Driver=usbfs, 1.5M |__ Port 4: Dev 3, If 0, Class=Communications, Driver=rndis_host, 480M |__ Port 4: Dev 3, If 1, Class=CDC Data, Driver=rndis_host, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M |__ Port 2: Dev 3, If 0, Class=Mass Storage, Driver=uas, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 4, If 2, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 1: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 1: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 7: Dev 3, If 0, Class=Vendor Specific Class, Driver=pl2303, 12M |__ Port 10: Dev 5, If 0, Class=Vendor Specific Class, Driver=pl2303, 12M Step #2, virsh start macOS, then I have, a) lsusb -t /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 3: Dev 26, If 0, Class=Human Interface Device, Driver=usbfs, 1.5M |__ Port 4: Dev 3, If 0, Class=Communications, Driver=rndis_host, 480M |__ Port 4: Dev 3, If 1, Class=CDC Data, Driver=rndis_host, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M |__ Port 2: Dev 3, If 0, Class=Mass Storage, Driver=uas, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 4, If 2, Class=Human Interface Device, Driver=usbfs, 12M |__ Port 1: Dev 4, If 0, Class=Human Interface Device, Driver=usbfs, 12M |__ Port 1: Dev 4, If 1, Class=Human Interface Device, Driver=usbfs, 12M |__ Port 7: Dev 3, If 0, Class=Vendor Specific Class, Driver=pl2303, 12M |__ Port 10: Dev 5, If 0, Class=Vendor Specific Class, Driver=pl2303, 12M b) Output from, journalctl -f | grep -v x11vnc (avoid x11vnc flooding), Dec 01 14:35:32 linuxServer audit[845332]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-d06d502a-904a-4b34-847d-debf1a3d76c7" pid=845332 comm="apparmor_parser" Dec 01 14:35:32 linuxServer kernel: audit: type=1400 audit(1606854932.259:190): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-d06d502a-904a-4b34-847d-debf1a3d76c7" pid=845332 comm="apparmor_parser" Dec 01 14:35:32 linuxServer audit[845341]: AVC apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-d06d502a-904a-4b34-847d-debf1a3d76c7" pid=845341 comm="apparmor_parser" Dec 01 14:35:32 linuxServer kernel: audit: type=1400 audit(1606854932.451:191): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-d06d502a-904a-4b34-847d-debf1a3d76c7" pid=845341 comm="apparmor_parser" Dec 01 14:35:32 linuxServer audit[845345]: AVC apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-d06d502a-904a-4b34-847d-debf1a3d76c7" pid=845345 comm="apparmor_parser" Dec 01 14:35:32 linuxServer kernel: audit: type=1400 audit(1606854932.643:192): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-d06d502a-904a-4b34-847d-debf1a3d76c7" pid=845345 comm="apparmor_parser" Dec 01 14:35:32 linuxServer audit[845352]: AVC apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-d06d502a-904a-4b34-847d-debf1a3d76c7" pid=845352 comm="apparmor_parser" Dec 01 14:35:32 linuxServer kernel: audit: type=1400 audit(1606854932.839:193): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-d06d502a-904a-4b34-847d-debf1a3d76c7" pid=845352 comm="apparmor_parser" Dec 01 14:35:32 linuxServer kernel: virbr0: port 2(vnet0) entered blocking state Dec 01 14:35:32 linuxServer kernel: virbr0: port 2(vnet0) entered disabled state Dec 01 14:35:32 linuxServer kernel: device vnet0 entered promiscuous mode Dec 01 14:35:32 linuxServer kernel: virbr0: port 2(vnet0) entered blocking state Dec 01 14:35:32 linuxServer kernel: virbr0: port 2(vnet0) entered listening state Dec 01 14:35:32 linuxServer NetworkManager[1648]: [1606854932.8545] manager: (vnet0): new Tun device (/org/freedesktop/NetworkManager/Devices/13) Dec 01 14:35:32 linuxServer systemd-udevd[845358]: Using defau
[Bug 1906155] Re: USB Passthrough Fails on Start, Needs domain Reset
Sure, will add - NP! One comment on (2) ... I can't say if this happens with other guests or not, as I only bind this USB device to this particular (guest) OS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906155 Title: USB Passthrough Fails on Start, Needs domain Reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906155] Re: USB Passthrough Fails on Start, Needs domain Reset
Sure, NP at all! Let me try to answer, and yell if you need more details - I will get them for you. 1) Reset ... meaning if I start the domain with 'virsh start macOS' => no USB passthrough (Logitech nano receiver in this case). So then, I 'virsh reset macOS' ... USB passthrough works fine! But always needs the reset after start. Make sense? 2) Can't really check that, as I never get in to the guest OS. I can't even get into the UEFI, given that the passthrough device is a receiver for a keyboard and mouse. So it's right at the start where it's not available ... or better said, it's not available / working right from the start. 3) Sure, NP at all! Do you want me to filter journalctl, to only capture a specific target (e.g. libvirtd)? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906155 Title: USB Passthrough Fails on Start, Needs domain Reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899633] Re: Repeated kernel warnings/stacktraces with kernel 5.4 and newer
Confirmed that with v4l2loopback-dkms 0.12.3-1ubuntu0.1, configured devices are not correctly advertised. This breaks Zoom, Cheese, etc. Compiling v4l2loopback from upstream source works correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899633 Title: Repeated kernel warnings/stacktraces with kernel 5.4 and newer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l2loopback/+bug/1899633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694808] Re: Passthrough USB Host Keyboard doesn't work on Q35 platform on boot-up
Hi, Seeing this same thing! And I'm on Ubuntu 20.10, so pretty current :-). vt82c686b-usb-uhci doesn't seem to be accessible any more, but trying qemu-xhci => no joy, still have to reset the VM after each startup, to get the keyboard and mouse working. Is this expected? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694808 Title: Passthrough USB Host Keyboard doesn't work on Q35 platform on boot-up To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1694808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901274] [NEW] Install of the boot loader failed
Public bug reported: I was running Ubuntu 18.04 which was working fine. I attempted to update to 20.4. The update failed miserably (many panic messages)and the automatic recovery to 18.04 failed also. I then ran Ubuntu 16.04 from disk, which worked, but would not install. I ran "boot-repair" which also failed (exited). I created a new disk image of 18.04 which seemed to install and I am using it to send this message, but grub-installer would not load on any of the Ubuntu partitions on my hardware. I will need to manually install a boot loader and I have no idea how to do that. Please help, else this machine will become a Windows 7 machine and I do not have any use for that OS. Steve ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.15 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CasperVersion: 1.394.3 Date: Fri Oct 23 18:32:15 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901274 Title: Install of the boot loader failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1901274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900649] [NEW] Xorg crash
Public bug reported: The computer freezes the fan speeds up and the screen goes to a black screen showing the operations the computer is doing before it shuts down ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 20 01:00:24 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. UHD Graphics 630 (Mobile) [1a58:2001] NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. GP106M [GeForce GTX 1060 Mobile] [1a58:2001] MachineType: Razer Blade ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=dd0ac3c7-c88c-4b4a-90ea-b9a430d6e2c3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2019 dmi.bios.vendor: Razer dmi.bios.version: 01.02 dmi.board.name: DANA_MB dmi.board.vendor: Razer dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr01.02:bd05/21/2019:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr: dmi.product.family: 1A582001 Razer Blade dmi.product.name: Blade dmi.product.sku: RZ09-02705E75 dmi.product.version: 1.04 dmi.sys.vendor: Razer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash focal ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900649 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1900649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900193] [NEW] Computer randomly freezes, the fan speeds up, and I lose wifi connection
Public bug reported: The computer randomly freezes, the fan speeds up, and I lose wifi connection. I've noticed that whatever browser I use takes up the majority of the cpu... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 16 17:01:50 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. UHD Graphics 630 (Mobile) [1a58:2001] NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. GP106M [GeForce GTX 1060 Mobile] [1a58:2001] MachineType: Razer Blade ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-51-generic root=UUID=dd0ac3c7-c88c-4b4a-90ea-b9a430d6e2c3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2019 dmi.bios.vendor: Razer dmi.bios.version: 01.02 dmi.board.name: DANA_MB dmi.board.vendor: Razer dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr01.02:bd05/21/2019:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr: dmi.product.family: 1A582001 Razer Blade dmi.product.name: Blade dmi.product.sku: RZ09-02705E75 dmi.product.version: 1.04 dmi.sys.vendor: Razer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal performance ubuntu ** Summary changed: - Computer randomly freezes, the fan speeds up, and I loose wifi connection + Computer randomly freezes, the fan speeds up, and I lose wifi connection -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900193 Title: Computer randomly freezes, the fan speeds up, and I lose wifi connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1900193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1899289] Re: freeze
The file comes up empty... On Mon, Oct 12, 2020 at 2:01 AM Daniel van Vugt <1899...@bugs.launchpad.net> wrote: > Next time the problem happens please: > > 1. Reboot > > 2. Run: > > journalctl -b-1 > prevboot.txt > > and attach the resulting text file here. > > > ** Package changed: xorg (Ubuntu) => ubuntu > > ** Tags added: hybrid nvidia > > ** Changed in: ubuntu >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1899289 > > Title: > freeze > > Status in Ubuntu: > Incomplete > > Bug description: > At seemingly random times the computer freezes and the fan will start > going really hard... Ive noticed that the cpu usage is unnaturally > high when i use the internet... no matter which browser I use. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 > Uname: Linux 5.4.0-48-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: > '/proc/driver/nvidia/capabilities/gpu0' > .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: > '/proc/driver/nvidia/capabilities/mig' > .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: > '/proc/driver/nvidia/gpus/:01:00.0' > .proc.driver.nvidia.registry: Binary: "" > .proc.driver.nvidia.suspend: suspend hibernate resume > .proc.driver.nvidia.suspend_depth: default modeset uvm > .proc.driver.nvidia.version: >NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.66 Wed Aug 12 > 19:42:48 UTC 2020 >GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) > ApportVersion: 2.20.11-0ubuntu27.9 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Sat Oct 10 16:11:04 2020 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > GpuHangFrequency: Several times a day > GpuHangReproducibility: Seems to happen randomly > GpuHangStarted: Since a couple weeks or more > GraphicsCard: >Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 > [VGA controller]) > Subsystem: Razer USA Ltd. UHD Graphics 630 (Mobile) [1a58:2001] >NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev > a1) (prog-if 00 [VGA controller]) > Subsystem: Razer USA Ltd. GP106M [GeForce GTX 1060 Mobile] [1a58:2001] > MachineType: Razer Blade > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic > root=UUID=dd0ac3c7-c88c-4b4a-90ea-b9a430d6e2c3 ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > Title: Xorg freeze > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 05/21/2019 > dmi.bios.vendor: Razer > dmi.bios.version: 01.02 > dmi.board.name: DANA_MB > dmi.board.vendor: Razer > dmi.chassis.type: 10 > dmi.chassis.vendor: Razer > dmi.modalias: > dmi:bvnRazer:bvr01.02:bd05/21/2019:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr: > dmi.product.family: 1A582001 Razer Blade > dmi.product.name: Blade > dmi.product.sku: RZ09-02705E75 > dmi.product.version: 1.04 > dmi.sys.vendor: Razer > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.101-2 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 > version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+bug/1899289/+subscriptions > ** Attachment added: "Ubuntu.png" https://bugs.launchpad.net/bugs/1899289/+attachment/5422311/+files/Ubuntu.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899289 Title: freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1899289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899159] Re: SRU: backport Python 3.8.6 and 3.9.0 to 20.04 LTS
Hi, This backport appears to have introduced a regression. Permissions of /usr/local/lib/python3.8/dist-packages changed, disallowing non root access breaking policyd-spf. ** Attachment added: "1899159" https://bugs.launchpad.net/ubuntu/+source/python3.8/+bug/1899159/+attachment/5421845/+files/1899159 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899159 Title: SRU: backport Python 3.8.6 and 3.9.0 to 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-stdlib-extensions/+bug/1899159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899289] [NEW] freeze
Public bug reported: At seemingly random times the computer freezes and the fan will start going really hard... Ive noticed that the cpu usage is unnaturally high when i use the internet... no matter which browser I use. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.66 Wed Aug 12 19:42:48 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 10 16:11:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. UHD Graphics 630 (Mobile) [1a58:2001] NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. GP106M [GeForce GTX 1060 Mobile] [1a58:2001] MachineType: Razer Blade ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=dd0ac3c7-c88c-4b4a-90ea-b9a430d6e2c3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2019 dmi.bios.vendor: Razer dmi.bios.version: 01.02 dmi.board.name: DANA_MB dmi.board.vendor: Razer dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr01.02:bd05/21/2019:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr: dmi.product.family: 1A582001 Razer Blade dmi.product.name: Blade dmi.product.sku: RZ09-02705E75 dmi.product.version: 1.04 dmi.sys.vendor: Razer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899289 Title: freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1899289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898759] [NEW] Wifi randomly disconnects
Public bug reported: Randomly, my computer's fan will start going really hard and then it will completely freeze and disconnect from the wifi for up to 1 minute and then reconnects again... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: russellcape 2178 F pulseaudio /dev/snd/controlC0: russellcape 2178 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 6 13:00:02 2020 MachineType: Razer Blade ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=dd0ac3c7-c88c-4b4a-90ea-b9a430d6e2c3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2019 dmi.bios.vendor: Razer dmi.bios.version: 01.02 dmi.board.name: DANA_MB dmi.board.vendor: Razer dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr01.02:bd05/21/2019:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr: dmi.product.family: 1A582001 Razer Blade dmi.product.name: Blade dmi.product.sku: RZ09-02705E75 dmi.product.version: 1.04 dmi.sys.vendor: Razer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898759 Title: Wifi randomly disconnects To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851250] Re: [snap] chromium-browser snap cannot upload files outside ~
I'm noting that nearly a year after this has been reported there is still no fix and no workaround. It may be marked as *invalid* because it is a *feature* but there is no way to turn that feature off and get my work done. Please reopen and put a control to disable this mal-feature on the urgent to do list. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851250 Title: [snap] chromium-browser snap cannot upload files outside ~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895618] [NEW] ubuntu dock bounces when on bottom and auto-hide is active
Public bug reported: While dock is locked to the bottom of the screen and hidden while not in use, once un-hidden/activated it will bounce back and forth between hidden and un-hidden. This is much more apparent or frequent when there is a window that is either maximized or has a boarder near the bottom of the screen next to where the dock will be activated at (Usually the bottom 10 or 20 pixels of the screen). This is potentially a GNOME issues or an "Ubuntu Dock", issue. However, I don't have the time at the moment to diagnose this further. Attached is a video which shows the bug in action. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 14 22:19:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:07e1] Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07e1] InstallationDate: Installed on 2020-04-25 (143 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 005: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 1bcf:28b0 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5577 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=1a7811cb-1019-45cb-97af-94a5bf22c0c3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0MVD5F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd12/02/2018:svnDellInc.:pnInspiron5577:pvr1.1.3:rvnDellInc.:rn0MVD5F:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 5577 dmi.product.sku: 07E1 dmi.product.version: 1.1.3 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Attachment added: "Video of the bounce that I am talking about." https://bugs.launchpad.net/bugs/1895618/+attachment/5410901/+files/2020-09-14%2022-14-22.mkv -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895618 Title: ubuntu dock bounces when on bottom and auto-hide is active To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1895618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891875] [NEW] package snapd 2.44.3+20.04 failed to install/upgrade: package snapd is not ready for configuration cannot configure (current status 'half-installed')
Public bug reported: Unknown - new to Ubuntu ProblemType: Package DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.6 AptOrdering: snapd:amd64: Configure chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Aug 17 09:55:40 2020 DpkgTerminalLog: dpkg: error processing package snapd (--configure): package snapd is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package snapd is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2020-08-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 Snap: snapd 2.44.3 () Title: package snapd 2.44.3+20.04 failed to install/upgrade: package snapd is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891875 Title: package snapd 2.44.3+20.04 failed to install/upgrade: package snapd is not ready for configuration cannot configure (current status 'half- installed') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1891875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891092] Re: Fresh install of cockpit on 20.04 after patching can no longer manage virtual machines
Further update...works when you use the session option to create the VM (rather than system). Horribly slow though with all the negatives of using session rather than system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891092 Title: Fresh install of cockpit on 20.04 after patching can no longer manage virtual machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cockpit/+bug/1891092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891092] Re: Fresh install of cockpit on 20.04 after patching can no longer manage virtual machines
Been testing further. Based on errors relating to apparmor tried complain mode for libvirtd followed by reboot and completely disabling apparmor. However no difference and these messages are still in the logs. Seeing this error in the log: Unable to open /dev/kvm: Permission denied CODE_FILE ../../../src/util/virhostcpu.c CODE_FUNC virHostCPUGetTscInfo CODE_LINE 1338 LIBVIRT_CODE38 LIBVIRT_DOMAIN 0 LIBVIRT_SOURCE util.error PRIORITY3 SYSLOG_FACILITY 24 _AUDIT_LOGINUID 1000 _AUDIT_SESSION 2 _BOOT_ID8298d387029b4a00ab2c4ff8889ee65e _CAP_EFFECTIVE 0 _CMDLINE/usr/sbin/libvirtd --timeout=120 _COMM libvirtd _EXE/usr/sbin/libvirtd _GID1000 _HOSTNAME pdukvm02 _MACHINE_ID b8db10128faf4d6bb85f42a6bf07a3b8 _PID1337 _SELINUX_CONTEXTunconfined _SOURCE_REALTIME_TIMESTAMP 1597131226041764 _SYSTEMD_CGROUP /user.slice/user-1000.slice/user@1000.service/dbus.service _SYSTEMD_INVOCATION_ID 8bd95fa9bc554d5587ed2f307645b7f0 _SYSTEMD_OWNER_UID 1000 _SYSTEMD_SLICE user-1000.slice _SYSTEMD_UNIT user@1000.service _SYSTEMD_USER_SLICE -.slice _SYSTEMD_USER_UNIT dbus.service _TRANSPORT journal _UID1000 __CURSOR s=7a07741964f14008b73e6164241c5bad;i=3c21;b=8298d387029b4a00ab2c4ff8889ee65e;m=17975743;t=5ac9517634db1;x=72d57812f6b29d92 __MONOTONIC_TIMESTAMP 395794243 __REALTIME_TIMESTAMP1597131226041777 Preceded by: Failed to read AppArmor profiles list '/sys/kernel/security/apparmor/profiles': Permission denied CODE_FILE ../../../src/security/security_apparmor.c CODE_FUNC profile_status CODE_LINE 87 LIBVIRT_CODE38 LIBVIRT_DOMAIN 24 LIBVIRT_SOURCE util.error PRIORITY3 SYSLOG_FACILITY 24 _AUDIT_LOGINUID 1000 _AUDIT_SESSION 2 _BOOT_ID8298d387029b4a00ab2c4ff8889ee65e _CAP_EFFECTIVE 0 _CMDLINE/usr/sbin/libvirtd --timeout=120 _COMM libvirtd _EXE/usr/sbin/libvirtd _GID1000 _HOSTNAME pdukvm02 _MACHINE_ID b8db10128faf4d6bb85f42a6bf07a3b8 _PID1337 _SELINUX_CONTEXTunconfined _SOURCE_REALTIME_TIMESTAMP 1597131226002371 _SYSTEMD_CGROUP /user.slice/user-1000.slice/user@1000.service/dbus.service _SYSTEMD_INVOCATION_ID 8bd95fa9bc554d5587ed2f307645b7f0 _SYSTEMD_OWNER_UID 1000 _SYSTEMD_SLICE user-1000.slice _SYSTEMD_UNIT user@1000.service _SYSTEMD_USER_SLICE -.slice _SYSTEMD_USER_UNIT dbus.service _TRANSPORT journal _UID1000 __CURSOR s=7a07741964f14008b73e6164241c5bad;i=3c20;b=8298d387029b4a00ab2c4ff8889ee65e;m=1796c0aa;t=5ac951762b718;x=9fc636c6f52c48c2 __MONOTONIC_TIMESTAMP 395755690 __REALTIME_TIMESTAMP1597131226003224 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891092 Title: Fresh install of cockpit on 20.04 after patching can no longer manage virtual machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cockpit/+bug/1891092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891092] [NEW] Fresh install of cockpit on 20.04 after patching can no longer manage virtual machines
Public bug reported: Install 20.04, patch, install kvm, install cockpit. Attempt to create VM via web UI, appears momentarily then disappears and states no VM's. Querying via virsh shows the VM has been created. This used to work fine, and seems to have stopped with latest patches as of a week or so back. May have imagined but I think I saw recent patches for libvirtd? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cockpit 215-1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Aug 10 22:22:31 2020 InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: cockpit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cockpit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891092 Title: Fresh install of cockpit on 20.04 after patching can no longer manage virtual machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cockpit/+bug/1891092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874943] [NEW] can't install ubuntu for the first time :(
Public bug reported: help ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 19:17:16 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874943 Title: can't install ubuntu for the first time :( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1874943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863397] [NEW] inputlirc does not wait for usb devices to exist
Public bug reported: Description:Ubuntu 19.10 Release:19.10 inputlirc: Installed: 30-1 Candidate: 30-1 Version table: *** 30-1 500 500 http://au.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages 100 /var/lib/dpkg/status As shipped the inputlirc package fails to start because it cannot find the USB devices configured in /etc/default/inutlirc as these devices have not been created by the kernel (yet). This is because /lib/systemd/system/inputlirc.service pointed to from /etc/systemd/system/multi-user.target.wants/inputlirc.service has After="udev" which shows as unknown in syslog. inputlirc.service needs to be updated to have instread: Requires=systemd-udev-settle.service After=lircd.socket After=systemd-udev-settle.service ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: inputlirc 30-1 [modified: lib/systemd/system/inputlirc.service] ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sat Feb 15 14:21:34 2020 Dependencies: gcc-9-base 9.2.1-9ubuntu2 libc6 2.30-0ubuntu2 libgcc1 1:9.2.1-9ubuntu2 libidn2-0 2.2.0-2 libunistring2 0.9.10-2 InstallationDate: Installed on 2020-01-26 (19 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: inputlirc UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.inputlirc: [modified] mtime.conffile..etc.default.apport: 2020-01-27T00:21:00 mtime.conffile..etc.default.inputlirc: 2020-02-14T21:22:40.467965 ** Affects: inputlirc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/inputlirc/+bug/1863397/+attachment/5328291/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863397 Title: inputlirc does not wait for usb devices to exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inputlirc/+bug/1863397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1405873] Re: -json output not valid when -class filter used
One can see the full extent of the brokenness of the command (in all
versions I've seen) using
#!/usr/bin/env python3
from itertools import combinations, chain, repeat
from subprocess import check_output as sco
import json
cmd = ['lshw', '-json', '-quiet']
classes = 'system bus memory processor bridge display generic multimedia
storage network'.split()
if __name__ == '__main__':
for flags in chain(*(combinations(classes, n) for n in
range(len(classes:
flags = chain(*zip(repeat('-c'), flags))
flags = list(flags)
if True:
try:
json.loads(sco(cmd + flags))
print(" ".join(flags), "was OK")
except json.decoder.JSONDecodeError as e:
print(' '.join(flags))
print(e)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1405873
Title:
-json output not valid when -class filter used
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1405873/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1405873] Re: -json output not valid when -class filter used
https://github.com/lyonel/lshw/tree/B.02.18 outputs valid json with lshw -json -quiet though it does have the problem described in https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1593233 i.e. can only run as root, and crashes otherwise. Using git bisect, the change that broke output was https://github.com/lyonel/lshw/pull/28 See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929206 ** Bug watch added: Debian Bug tracker #929206 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929206 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1405873 Title: -json output not valid when -class filter used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1405873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1405873] Re: -json output not valid when -class filter used
this has actually got worse, as it now (as of 19.10 / 02.18.85-0.3 at least) breaks when no class is used e.g. $ lshw -json -quiet | python3 -m json.tool Expecting ',' delimiter: line 26, column 8 (char 785) lshw -xml | xmllint - seems to indicate xml output works ok, but the format is annoying :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1405873 Title: -json output not valid when -class filter used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1405873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851091] Re: Fresh Eoan upgrade fails to boot dom0 with message "decoding failed" (kernel 5.3.0)
Based on my testing with fresh installs of both Disco and Eoan the 4.9.2-0ubuntu5 version fixes the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851091 Title: Fresh Eoan upgrade fails to boot dom0 with message "decoding failed" (kernel 5.3.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1851091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855586] [NEW] Feature request: allow toggling between airplane mode/bluetooth/wifi/both
Public bug reported: When pressing the monitor config key, one can switch between internal/external/mirror/join It would be nice to have something analagous for airplane/wifi/bluetooth/both, maybe after a long press ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855586 Title: Feature request: allow toggling between airplane mode/bluetooth/wifi/both To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1855586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842954] Re: AMD GPU hang/crash/black screen after suspend(ing)
I'm also experiencing this problem after upgrading to Ubuntu 19.10. I'm using xserver-xorg-video-amdgpu 19.0.1-1ubuntu1 so either it's not completely fixed, or I'm experiencing a different but very similar issue. One of the linked bug reports suggested the crash occurs in the XFCE compositor. I tried disabling the compositor: xfconf-query -c xfwm4 -p /general/use_compositing -s false This seems to be a usable workaround for now, though it does introduce some visual glitches. -- More detail: After booting to login screen, if I select an "XFCE" or "Xubuntu" session and log in, the system crashes to a black screen and is unresponsive to Ctrl-Alt-F2 or Ctrl-Alt-Del or anything else I try. (Alt+SysRq+b does reboot though.) Selecting an "Ubuntu" session is fine. After rebooting, I see 232 lines in syslog like this: WARNING: CPU: 2 PID: 274 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_hw_sequencer.c:932 dcn10_verify_allow_pstate_change_high.cold+0xc/0x23d [amdgpu] -- Hardware and version info: $ cat /proc/cpuinfo model name : AMD Ryzen 5 2400G with Radeon Vega Graphics $ lsb_release -a Description:Ubuntu 19.10 Release:19.10 Codename: eoan $ uname -r 5.3.0-23-generic $ apt show xserver-xorg Version: 1:7.7+19ubuntu12 $ apt show xserver-xorg-core Version: 2:1.20.5+git20191008-0ubuntu1 $ apt show xserver-xorg-video-amdgpu Version: 19.0.1-1ubuntu1 $ xfce4-session --version xfce4-session 4.14.0 (Xfce 4.14) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842954 Title: AMD GPU hang/crash/black screen after suspend(ing) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1842954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6
On my X1 Carbon 4th gen, kernel 5.3.0-22-generic seems to have completely fixed the issue. Yay! $ uname -a Linux evenedric 5.3.0-22-generic #24-Ubuntu SMP Sat Nov 9 17:34:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808389 Title: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1808389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804841] Re: iwlwifi Microcode SW error detected. Restarting 0x2000000.
*** This bug is a duplicate of bug 1808389 *** https://bugs.launchpad.net/bugs/1808389 I was hoping a firmware update would solve the problem, but now it is significantly worse. The crashes happen so frequently that the machine locks up for a minute or two. Even the capslock light on the keyboard becomes unresponsive. This usually happens just after boot or coming out of suspend, but not always. $ uname -a Linux evenedric 5.3.0-19-generic #20-Ubuntu SMP Fri Oct 18 09:04:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ fwupdmgr get-devices 20FBCTO1WW System Firmware DeviceId: [redacted] Guid: [redacted] Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Version: 0.1.42 VersionLowest:0.1.31 VersionFormat:triplet Icon: computer Created: 2019-11-12 UEFI Device Firmware DeviceId: [redacted] Guid: [redacted] Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Version: 184.65.3590 VersionLowest:0.0.1 VersionFormat:triplet Icon: audio-card Created: 2019-11-12 UEFI Device Firmware DeviceId: [redacted] Guid: [redacted] Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Version: 0.1.12 VersionLowest:0.0.1 VersionFormat:triplet Icon: audio-card Created: 2019-11-12 UpdateState: success $ iw reg get global country US: DFS-FCC (2402 - 2472 @ 40), (N/A, 30), (N/A) (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS (5735 - 5835 @ 80), (N/A, 30), (N/A) (57240 - 63720 @ 2160), (N/A, 40), (N/A) phy#0 (self-managed) country 00: DFS-UNSET (2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, NO-160MHZ (2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ (2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ (5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN (5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN (5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN (5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN (5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN (5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN (5290 - 5310 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN (5310 - 5330 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN (5490 - 5510 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN (5510 - 5530 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN (5530 - 5550 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN (5550 - 5570 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN (5570 - 5590 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN (5590 - 5610 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN (5610 - 5630 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN (5630 - 5650 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN (5650 - 5670 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN (5670 - 5690 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN (5690 - 5710 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN (5710 - 5730 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN (5735 - 5755 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN (5755 - 5775 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN (5775 - 5795 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN (5795 - 5815 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN (5815 - 5835 @ 20), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-HT40PLUS, NO-80MHZ, NO-160MHZ, PASSIVE-SCAN [ 439.402427] [ cut here ] [ 439
[Bug 1848374] Re: apt remove of gstreamer also tries to remove ubuntu-desktop
As a point of order, how does one remove gstreamer and all of it's plugins so that a new one can be compiled and then installed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848374 Title: apt remove of gstreamer also tries to remove ubuntu-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1848374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848374] [NEW] apt remove of gstreamer also tries to remove ubuntu-desktop
Public bug reported: Ubuntu 18.04 after a fresh install i've noticed that there are several packages, that although seem innocuous, if removed will remove the entire desktop with it. The following example contains an attempt to remove gstreamer as it was install unintentionally with the extra software checkmark on install. However, attempting to remove gstreamer will also remove the desktop? That doesn't seem correct. sudo apt remove gstreamer1.0-alsa gstreamer1.0-libav gstreamer1.0-plugins-bad gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly gstreamer1.0-pulseaudio libgstreamer-plugins-bad1.0-0 libgstreamer-plugins-base1.0-0 libgstreamer-plugins-good1.0-0 libgstreamer1.0-0 Reading package lists... Done Building dependency tree Reading state information... Done Package 'gstreamer1.0-plugins-bad' is not installed, so not removed The following packages were automatically installed and are no longer required: liba52-0.7.4 libaacs0 libavfilter6 libavformat57 libavresample3 libbdplus0 libbluray2 libbrotli1 libbs2b0 libchromaprint1 libdvdnav4 libdvdread4 libflite1 libgme0 libmpeg2-4 libmysofa0 libnorm1 libopencore-amrnb0 libopencore-amrwb0 libopenmpt0 libpgm-5.2-0 libpostproc54 librubberband2 libsidplay1v5 libssh-gcrypt-4 libwoff1 libzmq5 Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: policykit-1-gnome The following packages will be REMOVED: apturl cheese deja-dup evince gdm3 gir1.2-gst-plugins-base-1.0 gir1.2-gstreamer-1.0 gir1.2-rb-3.0 gir1.2-totem-1.0 gir1.2-webkit2-4.0 gnome-calendar gnome-control-center gnome-getting-started-docs gnome-initial-setup gnome-online-accounts gnome-shell gnome-software gnome-software-plugin-snap gnome-todo gnome-user-docs gnome-user-guide gnome-video-effects gstreamer1.0-alsa gstreamer1.0-clutter-3.0 gstreamer1.0-fluendo-mp3 gstreamer1.0-gl gstreamer1.0-gtk3 gstreamer1.0-libav gstreamer1.0-packagekit gstreamer1.0-plugins-base gstreamer1.0-plugins-base-apps gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly gstreamer1.0-pulseaudio gstreamer1.0-tools gstreamer1.0-vaapi gstreamer1.0-x libcheese-gtk25 libcheese8 libclutter-gst-3.0-0 libdmapsharing-3.0-2 libedataserverui-1.2-2 libevview3-3 libfreerdp-client2-2 libgoa-backend-1.0-1 libgstreamer-gl1.0-0 libgstreamer-plugins-bad1.0-0 libgstreamer-plugins-base1.0-0 libgstreamer-plugins-good1.0-0 libgstreamer1.0-0 libreoffice-avmedia-backend-gstreamer librhythmbox-core10 libtotem0 libwebkit2gtk-4.0-37 libyelp0 mutter nautilus-share packagekit packagekit-tools remmina-plugin-rdp rhythmbox rhythmbox-plugin-alternative-toolbar rhythmbox-plugins shotwell totem totem-plugins ubuntu-desktop ubuntu-docs ubuntu-release-upgrader-gtk ubuntu-session ubuntu-software update-manager update-notifier yelp zenity The following NEW packages will be installed: policykit-1-gnome 0 upgraded, 1 newly installed, 75 to remove and 0 not upgraded. Need to get 24.0 kB of archives. After this operation, 134 MB disk space will be freed. Do you want to continue? [Y/n] The expected behavior is that after we remove gstreamer, we should still have the desktop. Had I proceeded, it is likely that the machine just would have refused to boot. ** Affects: apt (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/1848374 Title: apt remove of gstreamer also tries to remove ubuntu-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1848374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787857] Re: USB mouse cursor lags after random time of correct behaviour
I also found this issue recent days, my cpu is also AMD, but I can not solve the problem by put mouse in usb3 port, whatever usb3.0 or usb2.0 the issue happens. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787857 Title: USB mouse cursor lags after random time of correct behaviour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838878] Re: Branch 430 does not support K1100M
Perhaps even more problematic is that the .430 driver does not have support for the new T4 cards, whereas .418 does. I am not an expert on Nvidia drivers, but it is very surprising to me that the older version of the driver has support for a new piece of hardware where the new driver does not, but either way, it would be very useful to be able to install actual .418 driver on Ubuntu 18.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838878 Title: Branch 430 does not support K1100M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1838878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844585] [NEW] Surface Pro 1 - System can't install the grub loader and provides no option to examine the file system nor offers a remedy. Just stops.
Public bug reported: Installation proceeds as expected, prior to the grub installaiton. Simply states that it cannot install the loader and that the system will not be able to boot without it. (Of course) It doesn't offer any steps to possibly resolve or diagnose the issue. It simply requests to submit a bug, then falls on it's face and exits. This is independent of the linux version, USB formatting. I've tried many with the same results. Perhaps it's protected partition of sorts. Based on experience, the system will now boot to grub only and the manual commands to boot it will result in a stop at (initramfs) I hope this helps, and of course any advice is welcome. I'm sure that I'm not the only person who has had to contend with this. 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 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 18 14:55:25 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.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/1844585 Title: Surface Pro 1 - System can't install the grub loader and provides no option to examine the file system nor offers a remedy. Just stops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1844585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837444] Re: pstree seg fault
I tried this out on one of out systems affected and it definitely resolves the bug. Before: :~$ for ((i=0;i<20;i++)); do pstree -alp 2>&1 > /dev/null; done Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault Segmentation fault :~$ After: :~$ for ((i=0;i<20;i++)); do pstree -alp 2>&1 > /dev/null; done :~$ for ((i=0;i<20;i++)); do pstree -alp 2>&1 > /dev/null; done :~$ for ((i=0;i<20;i++)); do pstree -alp 2>&1 > /dev/null; done :~$ for ((i=0;i<20;i++)); do pstree -alp 2>&1 > /dev/null; done :~$ A cursory inspection of the output of pstree looks normal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837444 Title: pstree seg fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/psmisc/+bug/1837444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837444] Re: pstree seg fault
Unfortunately no. I have a system where it reproduces readily and others where it does not, but am unsure of what the difference between the systems is. Only obvious thing is that the bad system has 7000+ processes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837444 Title: pstree seg fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/psmisc/+bug/1837444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837444] [NEW] pstree seg fault
Public bug reported: As per https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815902 Perhaps Xenial needs to be upgraded to use 22.22?? ** Affects: psmisc (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/1837444 Title: pstree seg fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/psmisc/+bug/1837444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836979] Re: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed”
** Description changed: - I’m not exactly sure if this belongs here, libva, mesa, or upstream - somewhere. But, it doesn’t seem to be a Kodi bug, buggy is that program - is. + Buggy as Kodi is, this seems to be a problem specifically with mesa-va- + drivers. Kodi has worked just fine on my system, as recently as July 6th of this year, but yesterday (July 16) I tried Kodi again: I got a blank screen and a pause for a few moments, followed by an unceremonious crash-to- desktop. This happens every time I start Kodi, now. If I run it through the command-line, I get this: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so libva info: Found init function __vaDriverInit_1_1 libva info: va_openDriver() returns 0 kodi-x11: ../src/gallium/drivers/nouveau/nouveau_vp3_video.c:91: nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed. Aborted (core dumped) I’ve been using the same version of Kodi (“18.3 Git:20190621-89472b7”, package version 2:18.3+git20190621.1610-final-0bionic, from the Team- - XBMC PPA) since its release in June, but in between July 7th and 16th, I - did upgrade Nouveau: - - 2019-07-07 06:50:36 upgrade libdrm-nouveau2:amd64 2.4.95-1~18.04.1 2.4.97-1ubuntu1~18.04.1 - 2019-07-07 06:50:36 status half-configured libdrm-nouveau2:amd64 2.4.95-1~18.04.1 - 2019-07-07 06:50:36 status unpacked libdrm-nouveau2:amd64 2.4.95-1~18.04.1 - 2019-07-07 06:50:36 status half-configured libdrm-nouveau2:i386 2.4.95-1~18.04.1 - 2019-07-07 06:50:36 status half-installed libdrm-nouveau2:amd64 2.4.95-1~18.04.1 - 2019-07-07 06:50:37 status half-installed libdrm-nouveau2:amd64 2.4.95-1~18.04.1 - 2019-07-07 06:50:37 status unpacked libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 - 2019-07-07 06:50:37 status unpacked libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 - 2019-07-07 06:50:37 upgrade libdrm-nouveau2:i386 2.4.95-1~18.04.1 2.4.97-1ubuntu1~18.04.1 - 2019-07-07 06:50:37 status half-configured libdrm-nouveau2:i386 2.4.95-1~18.04.1 - 2019-07-07 06:50:37 status unpacked libdrm-nouveau2:i386 2.4.95-1~18.04.1 - 2019-07-07 06:50:37 status half-installed libdrm-nouveau2:i386 2.4.95-1~18.04.1 - 2019-07-07 06:50:38 status half-installed libdrm-nouveau2:i386 2.4.95-1~18.04.1 - 2019-07-07 06:50:38 status unpacked libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 - 2019-07-07 06:50:38 status unpacked libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 - - 2019-07-07 06:51:44 configure libdrm-nouveau2:amd64 2.4.97-ubuntu1~18.04.1 - 2019-07-07 06:51:44 status unpacked libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 - 2019-07-07 06:51:44 status half-configured libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 - 2019-07-07 06:51:44 status installed libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 - 2019-07-07 06:51:44 configure libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 - 2019-07-07 06:51:44 status unpacked libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 - 2019-07-07 06:51:44 status half-configured libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 - 2019-07-07 06:51:44 status installed libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 - - (Another reason I’m guessing this is a Nouveau problem is because I - later tried switching to the official NVidia drivers, didn’t get this - bug, and then later encountered a distinct yet worse bug that locks up - the whole system. So, now I’m back to using Nouveau.) + XBMC PPA) since its release in June, but in between July 6th and 16th, I + did upgrade the Mesa packages, from 18.2.8-0ubuntu0~18.04.2 + 19.0.2-1ubuntu1.1~18.04.1. If I downgrade the “mesa-va-drivers” package + to 18.0.0~rc5-1ubuntu1 (the version in the base, non-updates Bionic + repository), however, Kodi works again, without even requiring me to + restart my machine. So, this is likely a problem with “mesa-va-drivers”. I tried looking in Xorg.0.log: [ 17185.557] (II) NOUVEAU(0): EDID vendor "SEC", prod id 12620 [ 17185.557] (II) NOUVEAU(0): Printing DDC gathered Modelines: [ 17185.558] (II) NOUVEAU(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446 1526 768 770 775 790 -hsync -vsync (47.4 kHz eP) …that’s all that appears in the log when I try to load Kodi and a crash happens. I’m using Ubuntu MATE 18.04.2 LTS 64-bit on a Compaq Presario CQ60; if you need more information, I’ve attached a hardinfo report, too. I hope this bug can get fixed, soon. Thanks! ** No longer affects: xserver-xorg-video-nouveau (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836979 Title: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ub
[Bug 1836979] Re: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed”
Sweet mother of the Muses, I just downgraded the mesa-va-drivers package to 18.0.0~rc5-1ubuntu1 (since that’s the one from the non-updates Bionic repository) and Kodi works again! Then, this is a problem specifically with the mesa-va-drivers package. I’ll have to update the description accordingly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836979 Title: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836979] Re: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed”
There was an update to Mesa over in the Ubuntu-X-Swat PPA today (by which I mean the “Updates” one), from 19.0.2-1ubuntu1.1~18.04.1 to 19.0.8-0ubuntu0~18.04.1. …Sadly, as I discovered—after installing the updates, then restarting and trying Kodi again—this bug is still present and still works exactly the same. (While I’m here, does anyone know how I would file a bug with the nvidia-340 package? I mean, I don’t know how much we can do about that driver, given its proprietary nature, but I want to try, at least. I just want one of my graphics drivers working so I can use my media player again… (sigh)) ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836979 Title: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836979] Re: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed”
In that same update, I also upgraded the Mesa package: 2019-07-07 06:50:41 upgrade libegl-mesa0:amd64 18.2.8-0ubuntu0~18.04.2 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:50:41 status half-configured libegl-mesa0:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:41 status unpacked libegl-mesa0:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:41 status half-installed libegl-mesa0:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:42 status half-installed libegl-mesa0:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:42 status unpacked libegl-mesa0:amd64 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:50:42 status unpacked libegl-mesa0:amd64 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:50:42 upgrade libgbm1:amd64 18.2.8-0ubuntu0~18.04.2 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:50:42 status half-configured libgbm1:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:43 status unpacked libgbm1:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:43 status half-installed libgbm1:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:43 status half-installed libgbm1:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:43 status unpacked libgbm1:amd64 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:50:43 status unpacked libgbm1:amd64 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:50:43 install libllvm8:i386 1:8-3~ubuntu18.04.1 2019-07-07 06:50:43 status half-installed libllvm8:i386 1:8-3~ubuntu18.04.1 2019-07-07 06:50:48 status unpacked libllvm8:i386 1:8-3~ubuntu18.04.1 2019-07-07 06:50:48 status unpacked libllvm8:i386 1:8-3~ubuntu18.04.1 2019-07-07 06:50:49 upgrade libgl1-mesa-dri:amd64 18.2.8-0ubuntu0~18.04.2 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:50:49 status half-configured libgl1-mesa-dri:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:49 status unpacked libgl1-mesa-dri:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:49 status half-configured libgl1-mesa-dri:i386 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:49 status half-installed libgl1-mesa-dri:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:51 status half-installed libgl1-mesa-dri:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:51 status unpacked libgl1-mesa-dri:amd64 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:50:51 status unpacked libgl1-mesa-dri:amd64 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:50:51 upgrade libgl1-mesa-dri:i386 18.2.8-0ubuntu0~18.04.2 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:50:51 status half-configured libgl1-mesa-dri:i386 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:51 status unpacked libgl1-mesa-dri:i386 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:52 status half-installed libgl1-mesa-dri:i386 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:53 status half-installed libgl1-mesa-dri:i386 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:54 status unpacked libgl1-mesa-dri:i386 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:50:54 status unpacked libgl1-mesa-dri:i386 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:50:54 install libllvm8:amd64 1:8-3~ubuntu18.04.1 2019-07-07 06:50:54 status half-installed libllvm8:amd64 1:8-3~ubuntu18.04.1 2019-07-07 06:50:58 status unpacked libllvm8:amd64 1:8-3~ubuntu18.04.1 2019-07-07 06:50:58 status unpacked libllvm8:amd64 1:8-3~ubuntu18.04.1 2019-07-07 06:50:59 upgrade libglx-mesa0:i386 18.2.8-0ubuntu0~18.04.2 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:50:59 status half-configured libglx-mesa0:i386 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:59 status unpacked libglx-mesa0:i386 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:59 status half-configured libglx-mesa0:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:59 status half-installed libglx-mesa0:i386 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:59 status half-installed libglx-mesa0:i386 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:51:00 status unpacked libglx-mesa0:i386 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:51:00 status unpacked libglx-mesa0:i386 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:51:00 upgrade libglx-mesa0:amd64 18.2.8-0ubuntu0~18.04.2 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:51:00 status half-configured libglx-mesa0:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:51:00 status unpacked libglx-mesa0:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:51:00 status half-installed libglx-mesa0:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:51:01 status half-installed libglx-mesa0:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:51:01 status unpacked libglx-mesa0:amd64 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:51:01 status unpacked libglx-mesa0:amd64 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:51:01 upgrade libglapi-mesa:amd64 18.2.8-0ubuntu0~18.04.2 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:51:01 status half-configured libglapi-mesa:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:51:01 status unpacked libglapi-mesa:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:51:01 status half-configured libglapi-mesa:i386 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:51:02 status half-installed libglapi-mesa:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:51:02 status half-installed libglapi-mesa:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:51:02 status unpacked libglapi-mesa:amd64 19.0.2-1ubuntu1.1~18.04.1 2019-07-07
[Bug 1836979] [NEW] Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed”
Public bug reported: I’m not exactly sure if this belongs here, libva, mesa, or upstream somewhere. But, it doesn’t seem to be a Kodi bug, buggy is that program is. Kodi has worked just fine on my system, as recently as July 7th of this year, but yesterday (July 16) I tried Kodi again: I got a blank screen and a pause for a few moments, followed by an unceremonious crash-to- desktop. This happens every time I start Kodi, now. If I run it through the command-line, I get this: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so libva info: Found init function __vaDriverInit_1_1 libva info: va_openDriver() returns 0 kodi-x11: ../src/gallium/drivers/nouveau/nouveau_vp3_video.c:91: nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed. Aborted (core dumped) I’ve been using the same version of Kodi (“18.3 Git:20190621-89472b7”, package version 2:18.3+git20190621.1610-final-0bionic, from the Team- XBMC PPA) since its release in June, but in between July 7th and 16th, I did upgrade Nouveau: 2019-07-07 06:51:44 configure libdrm-nouveau2:amd64 2.4.97-ubuntu1~18.04.1 2019-07-07 06:51:44 status unpacked libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 2019-07-07 06:51:44 status half-configured libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 2019-07-07 06:51:44 status installed libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 2019-07-07 06:51:44 configure libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 2019-07-07 06:51:44 status unpacked libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 2019-07-07 06:51:44 status half-configured libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 2019-07-07 06:51:44 status installed libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 (Another reason I’m guessing this is a Nouveau problem is because I later tried switching to the official NVidia drivers, didn’t get this bug, and then later encountered a distinct yet worse bug that locks up the whole system. So, now I’m back to using Nouveau.) I tried looking in Xorg.0.log: [ 17185.557] (II) NOUVEAU(0): EDID vendor "SEC", prod id 12620 [ 17185.557] (II) NOUVEAU(0): Printing DDC gathered Modelines: [ 17185.558] (II) NOUVEAU(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446 1526 768 770 775 790 -hsync -vsync (47.4 kHz eP) …that’s all that appears in the log when I try to load Kodi and a crash happens. I’m using Ubuntu MATE 18.04.2 LTS 64-bit on a Compaq Presario CQ60; if you need more information, I’ve attached a hardinfo report, too. I hope this bug can get fixed, soon. Thanks! ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Information on Tina’s hardware" https://bugs.launchpad.net/bugs/1836979/+attachment/5277708/+files/hardinfo_report_2019-07-17.html ** Description changed: I’m not exactly sure if this belongs here, libva, mesa, or upstream somewhere. But, it doesn’t seem to be a Kodi bug, buggy is that program is. Kodi has worked just fine on my system, as recently as July 7th of this year, but yesterday (July 16) I tried Kodi again: I got a blank screen and a pause for a few moments, followed by an unceremonious crash-to- desktop. This happens every time I start Kodi, now. If I run it through the command-line, I get this: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so libva info: Found init function __vaDriverInit_1_1 libva info: va_openDriver() returns 0 kodi-x11: ../src/gallium/drivers/nouveau/nouveau_vp3_video.c:91: nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed. Aborted (core dumped) I’ve been using the same version of Kodi (“18.3 Git:20190621-89472b7”, package version 2:18.3+git20190621.1610-final-0bionic, from the Team- - XBMC PPA) for months, but in between July 7th and 16th, I did upgrade - Nouveau: + XBMC PPA) since its release in June, but in between July 7th and 16th, I + did upgrade Nouveau: 2019-07-16 17:33:05 upgrade libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 2.4.97-1ubuntu1~18.04.1 2019-07-16 17:33:05 status half-configured libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 2019-07-16 17:33:05 status unpacked libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 2019-07-16 17:33:05 status half-installed libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 2019-07-16 17:33:05 status half-installed libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 2019-07-16 17:33:05 status unpacked libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 2019-07-16 17:33:05 status unpacked libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 2019-07-16 17:33:06 upgrade libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 2.4.97-1ubuntu1~18.04.1 2019-07-16 17:33:06 status half-configured libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 2019-07-16 17:33:06 status unpacked libdrm-nouveau2:i386 2.
[Bug 1769885] Re: Metview does not produce plots
Hi Alex,
I'm interested in this. I don't yet have an Ubuntu 19 system, but can
you confirm that the issue is only with plotting?
One quick thing to test is to write a new macro script like this:
print('hello')
and confirm that it runs ok. This will at least let us know that some things
are working.
If it's only a problem with plotting, then it's probably the same issue as was
found before in the configuration of the version of Metview supplied with
Ubuntu. There is always the possibility to build it from source if you have
experience of this - the bundle is usually the easiest way.
https://confluence.ecmwf.int/display/METV/The+Metview+Source+Bundle
We also have Metview available on conda. It's a bit experimental, but
you can install it from the conda-forge channel if you're familiar with
this environment.
Disclaimer: I'm the maintainer of Metview itself, but not of the Ubuntu
package for it.
Thanks,
Iain
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769885
Title:
Metview does not produce plots
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metview/+bug/1769885/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1017706] Re: [wishlist] ClamTk antivirus functionality within PCManFM
it is not working sir. you you can visit here for something special: - https://www.firstrankseoservices.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1017706 Title: [wishlist] ClamTk antivirus functionality within PCManFM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1017706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827640] Re: DHCP provided domain-name not respected while performing name lookups during install
>From what I can see, the most likely cluprit is the "dhclient-script". https://linux.die.net/man/8/dhclient-script I am out of time, but the installer's "/etc/dhcp/dhclient.conf" file should be checked. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827640 Title: DHCP provided domain-name not respected while performing name lookups during install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827640] [NEW] DHCP provided domain-name not respected while performing name lookups during install
Public bug reported: Ubuntu 18.04 is ignoring dhcp provided domain-name for name lookups during install. I suspect that this is also a problem for 19.04 but have not verified the behavior on that build as of yet, but I have also checked the release notes and cannot find anything pertaining to a fix either. This issue is being spawned from an ask-ubuntu question as I went there first for help. I am filing a bug since I am now satisfied that this has enough information and criteria to fit the description of a confirmed bug. The question this bug is being cloned from can be found at: https://askubuntu.com/questions/1139883/18-04-ignoring-dhcp-provided-domain-name-for-name-lookups-during-install I'm not sure what package this pertains to exactly as I am not sure where the problem is yet since correcting the resolve.conf file in the installer allows the install to continue as it should. However the issue could be in either dhclient it's self or a processed script which is triggered on each new dhcp lease. Either way, it's a pretty serious issue for anyone who has to use local network resources during an install and I hypothesize that this should be a simple fix that should help local installs a great deal. I could copy the images into the bug, but I'm hoping that isn't needed. There are a lot of images associated with this bug report since it deals with the installer. Those screen shots can be found on the attached askubuntu.com question. I ran into the problem while attempting to get a preconfigure file to perform an automated installation of ubuntu. See the following error: https://i.stack.imgur.com/Ns4qC.png The preconfigure file is passed in through the kernel parameters in an ipxe script like so: set theKernelParams auto=true fb=false interface=auto priority=critical url=ipxe/ubuntuks.conf However, this results in an error explaining that we cannot reach the server "ipxe". This is obviously not true from any machine in the lab and even not true from any other operating system that I use ipxe to install. Further investigation and looking at the console, it would appear that ubuntu is not respecting the dhcp provided domain-name when performing name lookups. This can be seen in the resolve.conf file and the lease made by dhclient. After returning an address from dhcp, dhclient should update the resolve.conf file to allow lookup of names that are not using the FQDN. screenshot: https://i.stack.imgur.com/rj68V.png After correcting the resolve.conf: https://i.stack.imgur.com/cCyzD.png Proof that ping works with short names after fixing the resolve.conf: https://i.stack.imgur.com/JPlkp.png After making the change to the resolve.conf file.. Setup continues with the preconfigure file like nothing ever happended.. Note: after install resolve.conf shows the following. https://i.stack.imgur.com/Sz8RL.png ** Affects: ubuntu Importance: Undecided Status: New ** Description changed: Ubuntu 18.04 is ignoring dhcp provided domain-name for name lookups during install. I suspect that this is also a problem for 19.04 but have not verified the behavior on that build as of yet, but I have also checked the release notes and cannot find anything pertaining to a fix either. This issue is being spawned from an ask-ubuntu question as I went there first for help. I am filing a bug since I am now satisfied that this has enough information and criteria to fit the description of a confirmed bug. The question this bug is being cloned from can be found at: https://askubuntu.com/questions/1139883/18-04-ignoring-dhcp-provided-domain-name-for-name-lookups-during-install I'm not sure what package this pertains to exactly as I am not sure where the problem is yet since correcting the resolve.conf file in the installer allows the install to continue as it should. However the issue could be in either dhclient it's self or a processed script which is triggered on each new dhcp lease. Either way, it's a pretty serious issue for anyone who has to use local network resources during an install and I hypothesize that this should be a simple fix that should help local installs a great deal. I could copy the images into the bug, but I'm hoping that isn't needed. There are a lot of images associated with this bug report since it deals with the installer. Those screen shots can be found on the attached askubuntu.com question. - I ran into the problem while attempting to get a preconfigure file to perform an automated installation of ubuntu. See the following error: - [![enter image description here][1]][1] - The preconfigure file is passed in through the kernel parameters in an + I ran into the problem while attempting to get a preconfigure file to perform an automated installation of ubuntu. See the following error: + https://i.stack.imgur.com/Ns4qC.png + + The preconfigure file is passed in through the kernel parameters in an ipxe script
[Bug 948191] Re: Please remove prevu from precise
Richard Hansen: “pbuilder create” (or “pbuilder --create”) gives me the error message: “mkdir: cannot create directory '/var/cache/pbuilder/build/13678': Permission denied”. Do I need to run pbuilder as root? Or, is there a setting I should change? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/948191 Title: Please remove prevu from precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prevu/+bug/948191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818140] Re: [Dell DW1560 / BCM20702A1] kobject_add_internal failed for hci0:11 with --EEXIST, don't try to register things with the same name in the same directory
Ubuntu 18.10 Bluez Version: 5.50-0ubuntu1 After changing batteries in my bluetooth mouse, it is connected but doesn't work (no movement or clicking). Fix is to re-pair it. ~$ dmesg | tail -40 [12650.520061] sysfs_warn_dup.cold.4+0x17/0x32 [12650.520064] sysfs_create_dir_ns+0xa9/0xd0 [12650.520067] kobject_add_internal+0xac/0x260 [12650.520071] ? kvasprintf+0x7f/0xd0 [12650.520073] kobject_add+0x7d/0xb0 [12650.520076] device_add+0x128/0x650 [12650.520092] hci_conn_add_sysfs+0x4b/0xc0 [bluetooth] [12650.520106] hci_conn_complete_evt.isra.47+0xc7/0x400 [bluetooth] [12650.520109] ? __switch_to_asm+0x34/0x70 [12650.520123] hci_event_packet+0x1670/0x27d0 [bluetooth] [12650.520124] ? __switch_to_asm+0x40/0x70 [12650.520126] ? __switch_to_asm+0x34/0x70 [12650.520127] ? __switch_to_asm+0x40/0x70 [12650.520129] ? __switch_to_asm+0x34/0x70 [12650.520130] ? __switch_to_asm+0x40/0x70 [12650.520132] ? __switch_to_asm+0x40/0x70 [12650.520144] hci_rx_work+0x190/0x380 [bluetooth] [12650.520148] ? __schedule+0x2a6/0x840 [12650.520153] process_one_work+0x20f/0x410 [12650.520156] worker_thread+0x34/0x400 [12650.520159] kthread+0x120/0x140 [12650.520162] ? pwq_unbound_release_workfn+0xd0/0xd0 [12650.520164] ? kthread_bind+0x40/0x40 [12650.520165] ret_from_fork+0x35/0x40 [12650.520168] kobject_add_internal failed for hci0:11 with -EEXIST, don't try to register things with the same name in the same directory. [12650.520172] Bluetooth: hci0: failed to register connection device [12650.582899] kobject_add_internal failed for 0005:05AC:030D.0008 (error: -2 parent: hci0:11) [12651.761999] Bluetooth: hci0: last event is not cmd complete (0x0f) [12667.896097] Bluetooth: hci0: last event is not cmd complete (0x0f) [12684.202210] Bluetooth: hci0: last event is not cmd complete (0x0f) [12688.792774] audit: type=1107 audit(1552483496.482:112): pid=1858 uid=105 auid=4294967295 ses=4294967295 subj==unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/NetworkManager" interface="org.freedesktop.NetworkManager" member="GetDevices" mask="send" name="org.freedesktop.NetworkManager" pid=4519 label="snap.chromium.chromium" peer_pid=2026 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? terminal=?' [12699.892349] Bluetooth: hci0: last event is not cmd complete (0x0f) [12716.204418] Bluetooth: hci0: last event is not cmd complete (0x0f) [12732.080523] Bluetooth: hci0: last event is not cmd complete (0x0f) [12747.954625] Bluetooth: hci0: last event is not cmd complete (0x0f) [12764.078740] Bluetooth: hci0: last event is not cmd complete (0x0f) [12779.952841] Bluetooth: hci0: last event is not cmd complete (0x0f) [12796.084949] Bluetooth: hci0: last event is not cmd complete (0x0f) [12812.215051] Bluetooth: hci0: last event is not cmd complete (0x0f) ~$ dpkg --status bluez | grep '^Version:' Version: 5.50-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818140 Title: [Dell DW1560 / BCM20702A1] kobject_add_internal failed for hci0:11 with --EEXIST, don't try to register things with the same name in the same directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093110] Re: [ubuntu-12.04] Phone Manager does NOT start
Also got this problem with gnome-phone-manager version 0.69 Ubuntu 18.04 andy@Dylan:~$ gnome-phone-manager (gnome-phone-manager:18615): Bluetooth-CRITICAL **: 17:03:40.879: bluetooth_chooser_button_set_property: assertion 'str == NULL || bluetooth_verify_address (str)' failed ** Message: 17:03:40.908: New connection device is empty (not changed) ** Message: 17:03:40.909: New connection device is empty (not changed) ** Message: 17:03:40.909: No device! ** Message: 17:03:40.909: Exiting connect thread ** Message: 17:04:00.891: Auto-retrying the connection ** Message: 17:04:00.891: New connection device is empty (not changed) ** Message: 17:04:00.892: New connection device is empty (not changed) ** Message: 17:04:00.892: No device! ** Message: 17:04:00.893: Exiting connect thread ** Message: 17:04:20.898: Auto-retrying the connection ** Message: 17:04:20.898: New connection device is empty (not changed) ** Message: 17:04:20.899: New connection device is empty (not changed) ** Message: 17:04:20.899: No device! ** Message: 17:04:20.900: Exiting connect thread ** Message: 17:04:40.909: Auto-retrying the connection ** Message: 17:04:40.909: New connection device is empty (not changed) ** Message: 17:04:40.910: New connection device is empty (not changed) ** Message: 17:04:40.910: No device! ** Message: 17:04:40.911: Exiting connect thread ** Message: 17:05:00.910: Auto-retrying the connection ** Message: 17:05:00.910: New connection device is empty (not changed) ** Message: 17:05:00.911: New connection device is empty (not changed) ** Message: 17:05:00.911: No device! ** Message: 17:05:00.912: Exiting connect thread ** Message: 17:05:20.910: Auto-retrying the connection ** Message: 17:05:20.910: New connection device is empty (not changed) ** Message: 17:05:20.911: New connection device is empty (not changed) ** Message: 17:05:20.911: No device! ** Message: 17:05:20.912: Exiting connect thread ** Message: 17:05:40.909: Auto-retrying the connection ** Message: 17:05:40.910: New connection device is empty (not changed) ** Message: 17:05:40.910: New connection device is empty (not changed) ** Message: 17:05:40.910: No device! ** Message: 17:05:40.912: Exiting connect thread ** Message: 17:06:00.909: Auto-retrying the connection ** Message: 17:06:00.910: New connection device is empty (not changed) ** Message: 17:06:00.910: New connection device is empty (not changed) ** Message: 17:06:00.910: No device! ** Message: 17:06:00.911: Exiting connect thread -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093110 Title: [ubuntu-12.04] Phone Manager does NOT start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-phone-manager/+bug/1093110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744582] Re: python3-tables incorrectly depends on python
/usr/bin/ptrepack in python3-tables tries to use python2 (/usr/bin/python), which will not work if python-tables is not installed. Same for pt2to3, ptdump and pttree. nctoh5 is missing, though the man page is present. It's also absent when I install to a 3.7 virtualenv. The other commands are present and run with python3 in the VE. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744582 Title: python3-tables incorrectly depends on python To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pytables/+bug/1744582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811029] Re: Package installation fails when attempting to download GeoIP database files
Oops, was meant for geoip-database-contrib. My bad. ** Package changed: geoip-database (Ubuntu) => geoip-database-contrib (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811029 Title: Package installation fails when attempting to download GeoIP database files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoip-database-contrib/+bug/1811029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811029] [NEW] Package installation fails when attempting to download GeoIP database files
Public bug reported: Selecting previously unselected package geoip-database-contrib. dpkg: considering removing geoip-database in favour of geoip-database-contrib ... dpkg: yes, will remove geoip-database in favour of geoip-database-contrib (Reading database ... 46544 files and directories currently installed.) Preparing to unpack geoip-database-contrib_1.19_all.deb ... Unpacking geoip-database-contrib (1.19) ... Setting up geoip-database-contrib (1.19) ... debconf: unable to initialize frontend: Dialog debconf: (TERM is not set, so the dialog frontend is not usable.) debconf: falling back to frontend: Readline debconf: unable to initialize frontend: Readline debconf: (This frontend requires a controlling tty.) debconf: falling back to frontend: Teletype Downloading: http://geolite.maxmind.com/download/geoip/database/GeoLiteCountry/GeoIP.dat.gz Failed to download http://geolite.maxmind.com/download/geoip/database/GeoLiteCountry/GeoIP.dat.gz Downloading: http://geolite.maxmind.com/download/geoip/database/GeoIPv6.dat.gz Downloading: http://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz Failed to download http://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz Downloading: http://geolite.maxmind.com/download/geoip/database/GeoLiteCityv6-beta/GeoLiteCityv6.dat.gz Downloading: http://geolite.maxmind.com/download/geoip/database/asnum/GeoIPASNum.dat.gz Failed to download http://geolite.maxmind.com/download/geoip/database/asnum/GeoIPASNum.dat.gz Downloading: http://geolite.maxmind.com/download/geoip/database/asnum/GeoIPASNumv6.dat.gz Creating config file /etc/cron.d/geoip-database-contrib with new version update-alternatives: error: alternative path /usr/share/GeoIP/GeoLiteCity.dat doesn't exist dpkg: error processing package geoip-database-contrib (--install): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: geoip-database-contrib This is due to Maxmind retiring their v1 geolite database. https://blog.maxmind.com/2018/01/02/discontinuation-of-the-geolite- legacy-databases/ The new versions are at URLs but - more importantly - are in a completely different format. ** Affects: geoip-database-contrib (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/1811029 Title: Package installation fails when attempting to download GeoIP database files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoip-database-contrib/+bug/1811029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807480] [NEW] [HP Pavilion Laptop 15-cd0xx, Realtek ALC295, Mic, Internal] Underruns, dropouts or crackling sound
Public bug reported: Whether I record with aux earbuds(with mics) or the internal mic I hear crackling with each sound. I tried using this https://wiki.ubuntu.com/Audio/PositionReporting but with no success. What should I do? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rgundlach2 2214 F pulseaudio /dev/snd/controlC0: rgundlach2 2214 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 7 20:37:12 2018 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: Built-in Audio - HD-Audio Generic Symptom_Jack: Mic, Internal Symptom_PulseAudioLog: Dec 07 20:31:09 hp-pavillion dbus-daemon[1336]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.36' (uid=121 pid=1788 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Dec 07 20:33:56 hp-pavillion pulseaudio[1788]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [HP Pavilion Laptop 15-cd0xx, Realtek ALC295, Mic, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2018 dmi.bios.vendor: AMI dmi.bios.version: F.26 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8353 dmi.board.vendor: HP dmi.board.version: 37.34 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.26:bd07/25/2018:svnHP:pnHPPavilionLaptop15-cd0xx:pvr:rvnHP:rn8353:rvr37.34:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cd0xx dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-12-07T20:19:52.343950 ** Affects: alsa-driver (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/1807480 Title: [HP Pavilion Laptop 15-cd0xx, Realtek ALC295, Mic, Internal] Underruns, dropouts or crackling sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1807480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768166] Re: Random crashes
I just encountered the problem again, after upgrading to libpinyin-1.10.0, but we can temporarily solve the problem if we delete this two file: ~/.cache/ibus/libpinyin/opengram.dbin ~/.cache/ibus/libpinyin/user_bigram.db and I got in this bug again, after deleting it for about 20 days -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768166 Title: Random crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1768166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796606] Re: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call
When I first started getting these crashes, they were triggered by attaching an external monitor, but that problem seems to have been fixed. Now, I am getting crashes when I put my laptop to sleep and then wake it up. It also destroys screen and tmux sessions somehow, so these crashes have about the same effect on the user as a kernel panic. Yet another way that systemd is broken, I guess? There was a [similar bug](https://bbs.archlinux.org/viewtopic.php?id=224570) reported on Arch Linux, where the redshift extension was blamed as the culprit (though no explanation was given about his this was determined or what the mechanism might be. I'm going to try disabling Night Mode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796606 Title: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.
I got this error to go away by changing my selection from "Send report automatically" to "Show dialog for each error before reporting" and rebooting". When I checked the logs, the error was not there. If I revert to "... automatically" and reboot I can get the error to appear again. Shouldn't the importance of this get changed especially if it means that error reports aren't being generated and sent out? Ubuntu 18.10 x86_64, 4.18.0-10-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: [FAILED] Failed to start Process error reports when automatic reporting is enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799789] Re: gnome-shell segfaults when external monitor attached or detached
Following step 3, I was able to file a crash report as bug 1800027. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799789 Title: gnome-shell segfaults when external monitor attached or detached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799789] Re: gnome-shell segfaults when external monitor attached or detached
Oops. Browser gremlins autofilled the wrong package name while I was filing the bug. ** Package changed: ubuntu-release-upgrader (Ubuntu) => gnome-shell (Ubuntu) ** Description changed: + I recently updated to Ubuntu 18.10, and I seem to have hit a new bug + with gnome-shell/wayland. + When an external monitor is attached or detached, gnome-shell crashes with a segmentation fault and falls back to a gdm session. This appears in dmesg : [97490.001835] gnome-shell[9151]: segfault at fbc8 ip 7fdd607f7ea8 sp 7ffd8cf7b270 error 5 in libst-1.0.so[7fdd607d1000+2b000] - [97490.001841] Code: 00 00 48 8d 3d 77 78 00 00 e9 54 9c fd ff 0f 1f 40 00 41 57 41 56 41 55 41 54 55 53 48 83 ec 28 48 63 1d fb 74 01 00 48 01 fb <48> 8b 6b 08 48 85 ed 74 17 48 83 c4 28 48 89 e8 5b 5d 41 5c 41 5d + [97490.001841] Code: 00 00 48 8d 3d 77 78 00 00 e9 54 9c fd ff 0f 1f 40 00 41 57 41 56 41 55 41 54 55 53 48 83 ec 28 48 63 1d fb 74 01 00 48 01 fb <48> 8b 6b 08 48 85 ed 74 17 48 83 c4 28 48 89 e8 5b 5d 41 5c 41 5d I've also attached the syslog file, starting from where the monitor was plugged in. Here are some of the highlights. First, the monitor is attached, and gnome-shell reaches for St.Bin and finds it already deallocated : Oct 24 12:37:00 evenedric kernel: [97488.486851] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Oct 24 12:37:01 evenedric gnome-shell[9151]: Object St.Bin (0x5619b14d30e0), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 24 12:37:01 evenedric gnome-shell[9151]: Object St.Bin (0x5619b14d30e0), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 24 12:37:01 evenedric org.gnome.Shell.desktop[9151]: == Stack trace for context 0x5619aee531c0 == Oct 24 12:37:01 evenedric org.gnome.Shell.desktop[9151]: #0 5619b71b1ff0 i resource:///org/gnome/shell/ui/userWidget.js:56 (7fdd27a55a60 @ 155) Oct 24 12:37:01 evenedric org.gnome.Shell.desktop[9151]: #1 7ffd8cf7d990 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7fdd27cb0b80 @ 71) Oct 24 12:37:01 evenedric org.gnome.Shell.desktop[9151]: #2 7ffd8cf7e5c0 b self-hosted:979 (7fdd27cf01f0 @ 440) - - This repeats several times with a few variations as the js interpreter in gnome-shell falls apart. Then the gnome-shell process is killed : + This repeats several times with a few variations as the js interpreter + in gnome-shell falls apart. Then the gnome-shell process is killed : Oct 24 12:37:01 evenedric kernel: [97490.001835] gnome-shell[9151]: segfault at fbc8 ip 7fdd607f7ea8 sp 7ffd8cf7b270 error 5 in libst-1.0.so[7fdd607d1000+2b000] - Oct 24 12:37:01 evenedric kernel: [97490.001841] Code: 00 00 48 8d 3d 77 78 00 00 e9 54 9c fd ff 0f 1f 40 00 41 57 41 56 41 55 41 54 55 53 48 83 ec 28 48 63 1d fb 74 01 00 48 01 fb <48> 8b 6b 08 48 85 ed 74 17 48 83 c4 28 48 89 e8 5b 5d 41 5c 41 5d + Oct 24 12:37:01 evenedric kernel: [97490.001841] Code: 00 00 48 8d 3d 77 78 00 00 e9 54 9c fd ff 0f 1f 40 00 41 57 41 56 41 55 41 54 55 53 48 83 ec 28 48 63 1d fb 74 01 00 48 01 fb <48> 8b 6b 08 48 85 ed 74 17 48 83 c4 28 48 89 e8 5b 5d 41 5c 41 5d This is then followed by the teardown for the whole session, eventually culminating in bringing up a new gdm login session. If you read through the attached syslog file, you can see the whole mess unfold. At about 12:37:05, I plug in an external mouse. Then colord makes a ton of noise for some reason, possibly related to the external monitor. Then I fire up my Bluetooth keyboard and log into a new session. This appears to be a regression. I've used this exact configuration (gdm3 and gnome-shell running in Wayland, with an external monitor that I use while I'm at work) for several Ubuntu, Gnome and Wayland releases. This appears to be a new issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799789 Title: gnome-shell segfaults when external monitor attached or detached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799789] [NEW] gnome-shell segfaults when external monitor attached or detached
Public bug reported: I recently updated to Ubuntu 18.10, and I seem to have hit a new bug with gnome-shell/wayland. When an external monitor is attached or detached, gnome-shell crashes with a segmentation fault and falls back to a gdm session. This appears in dmesg : [97490.001835] gnome-shell[9151]: segfault at fbc8 ip 7fdd607f7ea8 sp 7ffd8cf7b270 error 5 in libst-1.0.so[7fdd607d1000+2b000] [97490.001841] Code: 00 00 48 8d 3d 77 78 00 00 e9 54 9c fd ff 0f 1f 40 00 41 57 41 56 41 55 41 54 55 53 48 83 ec 28 48 63 1d fb 74 01 00 48 01 fb <48> 8b 6b 08 48 85 ed 74 17 48 83 c4 28 48 89 e8 5b 5d 41 5c 41 5d I've also attached the syslog file, starting from where the monitor was plugged in. Here are some of the highlights. First, the monitor is attached, and gnome-shell reaches for St.Bin and finds it already deallocated : Oct 24 12:37:00 evenedric kernel: [97488.486851] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Oct 24 12:37:01 evenedric gnome-shell[9151]: Object St.Bin (0x5619b14d30e0), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 24 12:37:01 evenedric gnome-shell[9151]: Object St.Bin (0x5619b14d30e0), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 24 12:37:01 evenedric org.gnome.Shell.desktop[9151]: == Stack trace for context 0x5619aee531c0 == Oct 24 12:37:01 evenedric org.gnome.Shell.desktop[9151]: #0 5619b71b1ff0 i resource:///org/gnome/shell/ui/userWidget.js:56 (7fdd27a55a60 @ 155) Oct 24 12:37:01 evenedric org.gnome.Shell.desktop[9151]: #1 7ffd8cf7d990 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7fdd27cb0b80 @ 71) Oct 24 12:37:01 evenedric org.gnome.Shell.desktop[9151]: #2 7ffd8cf7e5c0 b self-hosted:979 (7fdd27cf01f0 @ 440) This repeats several times with a few variations as the js interpreter in gnome-shell falls apart. Then the gnome-shell process is killed : Oct 24 12:37:01 evenedric kernel: [97490.001835] gnome-shell[9151]: segfault at fbc8 ip 7fdd607f7ea8 sp 7ffd8cf7b270 error 5 in libst-1.0.so[7fdd607d1000+2b000] Oct 24 12:37:01 evenedric kernel: [97490.001841] Code: 00 00 48 8d 3d 77 78 00 00 e9 54 9c fd ff 0f 1f 40 00 41 57 41 56 41 55 41 54 55 53 48 83 ec 28 48 63 1d fb 74 01 00 48 01 fb <48> 8b 6b 08 48 85 ed 74 17 48 83 c4 28 48 89 e8 5b 5d 41 5c 41 5d This is then followed by the teardown for the whole session, eventually culminating in bringing up a new gdm login session. If you read through the attached syslog file, you can see the whole mess unfold. At about 12:37:05, I plug in an external mouse. Then colord makes a ton of noise for some reason, possibly related to the external monitor. Then I fire up my Bluetooth keyboard and log into a new session. This appears to be a regression. I've used this exact configuration (gdm3 and gnome-shell running in Wayland, with an external monitor that I use while I'm at work) for several Ubuntu, Gnome and Wayland releases. This appears to be a new issue. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: gnome-shell libst segfault wayland -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799789 Title: gnome-shell segfaults when external monitor attached or detached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798729] Re: release upgrade from 18.04 to 18.10 cannot calculate upgrade, no reason given
autoremove doesn't do the trick. == $ sudo apt-get autoremove [sudo] password for russell: Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. == Removing emacs24-lucid directly allows do-release-upgrade to work. Neat! That error message should probably be amended to point users to log files in /var/log/dist-upgrade. I've been using Debian-based distros since before Ubuntu existed, and I had no idea it existed! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798729 Title: release upgrade from 18.04 to 18.10 cannot calculate upgrade, no reason given To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1798729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798729] [NEW] release upgrade from 18.04 to 18.10 cannot calculate upgrade, no reason given
Public bug reported: do-release-upgrade cannot calculate the upgrade, offers no useful insight as to why, and provides no way to see the actual underlying error. Reading cache Checking package manager Reading package lists... Done Building dependency tree Reading state information... Done Hit http://us.archive.ubuntu.com/ubuntu bionic InRelease Hit http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease Hit http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease Hit http://security.ubuntu.com/ubuntu bionic-security InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree Reading state information... Done Updating repository information Hit http://security.ubuntu.com/ubuntu cosmic-security InRelease Hit http://us.archive.ubuntu.com/ubuntu cosmic InRelease Hit http://us.archive.ubuntu.com/ubuntu cosmic-updates InRelease Hit http://us.archive.ubuntu.com/ubuntu cosmic-backports InRelease Fetched 0 B in 0s (0 B/s) Checking package manager Reading package lists... Done Building dependency tree Reading state information... Done Calculating the changes Calculating the changes Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. This can be caused by: * Upgrading to a pre-release version of Ubuntu * Running the current pre-release version of Ubuntu * Unofficial software packages not provided by Ubuntu If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. Restoring original system state Aborting Reading package lists... Done Building dependency tree Reading state information... Done === Command terminated with exit status 1 (Thu Oct 18 21:53:52 2018) === ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.27 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: GNOME Date: Thu Oct 18 21:49:00 2018 InstallationDate: Installed on 2015-12-17 (1036 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2018-10-19 (0 days ago) mtime.conffile..etc.update-manager.release-upgrades: 2018-10-18T21:43:55.313922 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798729 Title: release upgrade from 18.04 to 18.10 cannot calculate upgrade, no reason given To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1798729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
