[Bug 2064037] Re: GDM session crashes after returning from a screen-off.
I've reinstalled a fresh copy of 24.04 with extras enabled and recommended proprietary software installed, and I recorded a set of observations on a fresh system. I recorded journal logs and other stats in a similar format. I think I may have identified a culprit. The crash appears to only occur when screen lock is disabled. Maybe someone could try to reproduce? ** Attachment added: "debug-2024-05-05.zip" https://bugs.launchpad.net/ubuntu/+bug/2064037/+attachment/5775378/+files/debug-2024-05-05.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064037 Title: GDM session crashes after returning from a screen-off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2064037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064037] Re: GDM session crashes after returning from a screen-off.
I've updated my bios, but the issue seems to persist. It's still inconsistent. Sometimes it un-blanks without issue, sometimes I get the gray-screen-of-death, and sometimes it unblanks directly to the login page without a GSOD. I'll try any other debugging suggestions, including a OS-reinstall. The alternative is that I disable screen-blanking (which seems like a waste of power) or I revert to 22.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064037 Title: GDM session crashes after returning from a screen-off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2064037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064037] Re: GDM session crashes after returning from a screen-off.
Oh boy, so I've spent the past two days recording observations on this issue, and I see no clear patterns at all. I've created a zipfile with a text document called update.txt which contains my actions and observations. The basic pattern is: I do stuff, wait for the screen blank, un-blank and see if it crashes. Sometimes the crash happens and sometimes it does not. It also contains observations that detail what may be a separate issue (enabling / disabling screens had weird behavior, and I think I found a minor but fixable bug in the screenshot tool). I have 2 journalctl logs in there. After a few entries I realized I should start adding timestamps and normalize the observation format, so it goes from prose to a time / action / result / notes format after a point. In a few places I reference screenshots (which demonstrate the screenshot and monitor bug), those are included in the zipfile. Things that should be noted: At this point I've installed a fair bit of external software on the machine. I've included a list of it in apt_list.txt in the zipfile. I also have a development .pyenv in my home directory and my .bashrc will default to a specified virtualenv. So far I'm the only person who has reported this behavior. I'm wondering if its an issue with my hardware? I really like 24.04 so far, but this is a major issue for me. I may try a fresh install to make more observations with less uncontrolled variables. ** Attachment added: "debug-monitor-2024-05-02.zip" https://bugs.launchpad.net/ubuntu/+bug/2064037/+attachment/5774592/+files/debug-monitor-2024-05-02.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064037 Title: GDM session crashes after returning from a screen-off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2064037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064037] Re: GDM session crashes after returning from a screen-off.
I made an interesting observation. If I unplug all bug one monitor (I have been using 3 in tests up until now), the crash does not occur in X11. I have not tried wayland yet. I'm going to plug in a second monitor to check if it happens with 2, and then verify that it still occurs with 3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064037 Title: GDM session crashes after returning from a screen-off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2064037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064037] Re: GDM session crashes after returning from a screen-off.
Here is prevboot.txt Is my whoopsie-id something that should be kept private? I do have files in /var/crash that have timestamps from yesterday and today, but they do not seem to appear under https://errors.ubuntu.com/user/ even after I ran `ubuntu-bug ` ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+bug/2064037/+attachment/5773672/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064037 Title: GDM session crashes after returning from a screen-off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2064037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063970] Re: Enhanced tiling orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment.
I have noticed that it will happen in the wrong place and then go away from time to time. That bothers me a lot less than when it persists and obscures something I want to look at. I have no idea how to replicate it yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063970 Title: Enhanced tiling orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2063970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064037] Re: GDM session crashes after returning from a screen-off.
Update: I don't know what changed, (I did do an apt upgrade), but now the crash is happening for Wayland too whenever the screen powers off. It's very frustrating. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064037 Title: GDM session crashes after returning from a screen-off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2064037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056506] Re: ubuntu-dock 89 crashes on gnome-shell 45 with signal 6 when right clicking on the dock [clutter_actor_dispose: assertion failed: (priv->parent == NULL)]
I'm not sure if this is the same exact bug, my problem just seems to happen randomly not when necessarily when I close something, I'm still trying to identify a reproducible cause. My problem seems more similar to https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension- ubuntu-dock/+bug/2056633 but it is marked as a duplicate of this, so I'm posting my debug journalctl.txt info here. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2056506/+attachment/5772540/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056506 Title: ubuntu-dock 89 crashes on gnome-shell 45 with signal 6 when right clicking on the dock [clutter_actor_dispose: assertion failed: (priv->parent == NULL)] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2056506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064037] Re: GDM session crashes after returning from a screen-off.
Is there a resource you could point me to where I can learn what the security risks of public .crash files are? I'm interested to know what sensitive information could be contained in them. Interesting that the whoopsie-id seems to persist across OS installs, or maybe it's tied to my Ubuntu One account? I see crash reports on here going back to 2021. Recent crash reports on the 24.04 machine are: _usr_bin_gnome-shell.1000.crash - https://errors.ubuntu.com/oops/235257f3-0630-11ef-8b1f-fa163ec8ca8c _usr_bin_nautilus.1000.crash - https://errors.ubuntu.com/oops/1a6e3dfa-0409-11ef-9dc8-fa163ec44ecd _usr_bin_gnome-control-center.1000.crash - https://errors.ubuntu.com/oops/19d7ad54-0599-11ef-8b1c-fa163ec8ca8c _opt_google_chrome_chrome.1000.crash - https://errors.ubuntu.com/oops/13ddfcd0-0587-11ef-9dca-fa163ec44ecd I believe the gnome-shell is the relevant one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064037 Title: GDM session crashes after returning from a screen-off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2064037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064037] Re: GDM session crashes after returning from a screen-off.
I did have another "random" crash in the middle of a session. I was moving a window around. So it's not rela.ted to the main reason for this bug report, but I figure its relevant enough to attach the journalctl logs ** Attachment added: "wayland_crash_journalctl.log" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2064037/+attachment/5772177/+files/wayland_crash_journalctl.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064037 Title: GDM session crashes after returning from a screen-off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2064037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064037] Re: GDM session crashes after returning from a screen-off.
On the matrix chat Nils mentioned that "im on nvidia 550 atm and on wayland. i had some X11 crashes in the past and wayland does a much better job so far" So, I changed my session type to Wayland by logging out and using the gear by my username to select wayland. Doing that seems to have an issue with "Settings", clicking the setting gear or running `gnome-control- center` resulted in a segfault. I did some googling, and saw that this might be a nvidia driver issue, so I upgraded my drivers from `nvidia- driver-350` to `nvidia-driver-550`. After a reboot the segfault in `gnome-control-center` went away, and the logout crash also seems to be gone as well. I tested it by letting the screen dim, waiting 10 minutes, and then pressing a few keys. Instead of crashing it went right back to my session. Of course it would be nice if crashes didn't occur in the out-of-the-box Ubuntu 24.04 install, but in this case there seems to be a simple solution: Use Wayland and 550 drivers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064037 Title: GDM session crashes after returning from a screen-off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2064037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064037] Re: GDM session crashes after returning from a screen-off.
Also attaching the results of `sudo journalctl --dmesg --priority warning > journalctl_dmsg_warnings.log` it does seem to have some nvidia errors and tracebacks. It doesn't mean much to me, but perhaps it has useful information in it. ** Attachment added: "journalctl_dmsg_warnings.log" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2064037/+attachment/5772123/+files/journalctl_dmsg_warnings.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064037 Title: GDM session crashes after returning from a screen-off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2064037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064037] Re: GDM session crashes after returning from a screen-off.
I'm also experiencing intermittent crashes of the window manager - either gnome-shell or gdm3, not 100% sure. What I am sure of is that I'm getting forcibly logged out. I just experienced a crash when discussion this issue in matrix chat. There were a few things going on at the time. I did have steam and starcraft 2 open (running through steam's experimental proton). But that was in the background. In the foreground I was just moving a gvim window that had journalctl logs in it that I was going to copy into my chrome browser. I'm attaching the journalctl logs from that crash here as well, as perhaps these issues are related. ** Attachment added: "journalctl-gdm-crash-logs2.log" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2064037/+attachment/5772122/+files/journalctl-gdm-crash-logs2.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064037 Title: GDM session crashes after returning from a screen-off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2064037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064037] [NEW] GDM session crashes after returning from a screen-off.
Public bug reported: I've written an AskUbuntu question about this: https://askubuntu.com/questions/1511958/screen-lock-keeps-occuring- on-24-04-even-though-i-believe-ive-disabled-it/1512075#1512075 Originally I thought it was gnome not respecting my setting to prevent locking the screen after idling, but after discussing the issue on matrix (https://matrix.to/#/!EJhpCQHHqqcNicfiql:xentonix.net/$kPbn- fqDZgoG4s6PyQfki8tcSKJUpGH9QrXZSSV_vKY?via=decred.org=matrix.org=ubuntu.com) I think it is actually just a gdm or gnome-shell crash that happens when the PC idles, the screen turns off, and then I wake it. To summarize the symptom. I have the PC set to disable the screen after being idle for 5 minutes. I also set it such that it should not lock the session when this happens. (I want to turn on the screen and get right back to where I was without password overhead). What I've observed is that when I give the idle PC keyboard input, it wakes to a login screen, and when I login my windows from the previous session are completely gone (although tmux sessions are still alive). I've attached a relevant section of `journalctl --user` from around the time when I last tried to interact with the idle PC. I believe the "wake" event happens at `Apr 28 13:42:43` at which point we start seeing whoopsie messages: ``` Apr 28 13:42:44 toothbrush systemd[1]: Started whoopsie.service - crash report submission. ``` And then what looks like logs indicating that I was logged out and the previous session was ended: ``` Apr 28 13:42:56 toothbrush systemd[1]: run-user-1000-gvfs.mount: Deactivated successfully. Apr 28 13:42:57 toothbrush gdm-password][60731]: pam_unix(gdm-password:session): session closed for user joncrall Apr 28 13:42:57 toothbrush systemd[1]: session-61.scope: Deactivated successfully. Apr 28 13:42:57 toothbrush systemd[1]: session-61.scope: Consumed 12min 9.467s CPU time. Apr 28 13:42:57 toothbrush systemd-logind[1790]: Session 61 logged out. Waiting for processes to exit. Apr 28 13:42:57 toothbrush systemd-logind[1790]: Removed session 61. ``` The time from `13:42:44` to `13:43:07` where I get: ``` Apr 28 13:43:07 toothbrush systemd-logind[1790]: New session 221 of user joncrall. Apr 28 13:43:07 toothbrush systemd[1]: Started session-221.scope - Session 221 of User joncrall. ``` seems about right, because it takes a few seconds to go from de-idling the machine to seeing any sort of display. System Information: No LSB modules are available. Description:Ubuntu 24.04 LTS Release:24.04 # System Details Report --- ## Report details - **Date generated:** 2024-04-28 15:17:36 ## Hardware Information: - **Hardware Model:** ASUS ROG STRIX Z590-E GAMING WIFI - **Memory:** 128.0 GiB - **Processor:** 11th Gen Intel® Core™ i9-11900K × 16 - **Graphics:**NVIDIA GeForce RTX™ 3090 - **Graphics 1:** NVIDIA GeForce RTX™ 3090 - **Disk Capacity:** 45.0 TB ## Software Information: - **Firmware Version:**0232 - **OS Name:** Ubuntu 24.04 LTS - **OS Build:**(null) - **OS Type:** 64-bit - **GNOME Version:** 46 - **Windowing System:**X11 - **Kernel Version:** Linux 6.8.0-31-generic Nvidia versions: NVIDIA-SMI 535.171.04 Driver Version: 535.171.04 CUDA Version: 12.2 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gdm3 46.0-2ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 28 15:04:13 2024 InstallationDate: Installed on 2024-04-25 (3 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2024-04-25T18:50:53.891514 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ** Attachment added: "Journalctl logs" https://bugs.launchpad.net/bugs/2064037/+attachment/5772117/+files/journalctl_logs.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064037 Title: GDM session crashes after returning from a screen-off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2064037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
[Bug 2063970] Re: Enhanced tiling orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment.
I've confirmed it does happen when just using super+arrow and no mouse interaction. I still cannot get it to work reliably though. My monitor setup looks roughly like this: ``` +--+ |2 | +--+ | | |1 | +--+ | | +--+ | | |3 | | | | | | | +--+ +--+ ``` In one test, I was moving a window in monitor 3, and after pressing super+down the orange box appeared across the bottom of monitor 2, which is kinda weird. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063970 Title: Enhanced tiling orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063970] Re: Enhanced tiling orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment.
I was able to get a screenshot of the issue. I edited the images to remove sensitive information I was working with at the time, but the point is that I was moving around windows (I forget if I was using super+arrow or dragging to corners), and the issue happened. I'm still not sure exactly how to reproduce, but this at least provides some illustration of what is happening. Also note. I have 3 monitors. Two are in landscape and 1 is in portrait. Nothing of interest was in the other monitors. I'll also note I'm using nvidia graphics. I have an RTX 3090 driving the 3 monitors. ** Attachment added: "Screenshot of issue where orange overlay does not go away" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063970/+attachment/5771713/+files/gnome-shell-bug-reproduction.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063970 Title: Enhanced tiling orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063970] [NEW] Enhanced tiling orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment.
Public bug reported: I've got a fresh install of the first 24.04 release, and I'm seeing strange behavior related to super+arrow keys and the enhanced tiling. I've disabled tiling popups and tiling groups, but I like the quad blocks. The issue is when I'm moving around windows, sometimes the orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment. I'm not sure how to reproduce yet, but it's happened several times. Not sure if I'll be able to take a screenshot or not. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 27 16:06:49 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-04-25 (2 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) RelatedPackageVersions: mutter-common 46.0-1ubuntu9 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063970 Title: Enhanced tiling orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061167] Re: python3-distutils is not built for noble
Thanks all for the details. Assuming it is safe to be removed and that the new conflict in -proposed will help to do so automatically for users that upgrade, once mainlined. apt autoremove python3-distutils -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061167 Title: python3-distutils is not built for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-stdlib-extensions/+bug/2061167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
I can confirm the behaviour after a recent upgrade from mantic to noble and has also been reported in https://discourse.ubuntu.com/t/noble-dev- branch-why-does-the-keyring-stay-locked-upon-login-also-why-did-apt- install-work-but-apt-upgrade-fail/43979 Another oddity is, that I seem to have to type the password twice into the second, non-overlay password prompt, which has me type my password four times for a complete login. This may also be connected to recent changes about how the ssh-agent is initialised, which may or may not involve problems with the Keyring or the new GCR. (Does anybody know what the abbreviation means? Its readme stays silent about it.) - https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2061288 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2060575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061288] [NEW] Multiple conflicting SSH agents and SSH_AUTH_SOCK not set after upgrade to noble
Public bug reported: After upgrading mantic to noble, there are multiple SSH agents who are independently trying to set SSH_AUTH_SOCK, none of which is successful. 1. ~/.config/autostart/gnome-keyring-ssh.desktop (identical to /etc/xdg/autostart/gnome-keyring-ssh.desktop, if not modified) This will start the regular GNOME Keyring SSH Agent. It will set the Agent location to /run/user/1000/ssh, while the Socket is initialised at /run/user/1000/.ssh 2. If that one is not running, the user unit ssh-agent.service kicks in. It sets the Socket to live at /run/user/1000/openssh_agent 3. Parallely, there is also a GPG agent emulating SSH support gpg-agent- ssh.socket Socket at /run/user/1000/gnupg/S.gpg-agent.ssh 4. There is also the (new?) user unit gcr-ssh-agent.socket It sets its Socket to live at /run/user/1000/gcr/ssh --- The last one seems to be preferred by GNOME upstream nowadays, but also comes with caveats, as its unit does not set the SSH_AUTH_SOCK variable. This commit from !137 (see below) does not seem to be included in /usr/lib/systemd/user/gcr-ssh-agent.socket - https://gitlab.gnome.org/GNOME/gcr/-/commit/b12cc639949c4b548d84625b292a2aff1faaf195 Apparently it's solved upstream with the gcr 4.2.1 release. Installed is 4.2.0-4build1 There are discussions about how this is possibly resolved in - https://gitlab.gnome.org/GNOME/gnome-build-meta/-/issues/770 closed - https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/2623 open - https://gitlab.gnome.org/GNOME/gcr/-/issues/55 closed - https://gitlab.gnome.org/GNOME/gcr/-/merge_requests/137 merged - https://gitlab.gnome.org/GNOME/gcr/-/merge_requests/138 closed - https://gitlab.gnome.org/GNOME/gcr/-/merge_requests/139 reverts 137 Similar regressions around GCR (What does that abbreviation even mean? It's not explained in the readme) are described in the following, including other possible workarounds: - https://www.adamsdesk.com/posts/fix-gnome-keyring-ssh-auth-sock/ - https://bbs.archlinux.org/viewtopic.php?id=292403 ** Affects: gnome-keyring (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/2061288 Title: Multiple conflicting SSH agents and SSH_AUTH_SOCK not set after upgrade to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2061288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061167] [NEW] python3-distutils is not built for noble
Public bug reported: After upgrading to noble, there appears to be a regression between the to-be-installed python3-distutils package and its dependency python3-lib2to3. The old packages from mantic remain installed. python3-distutils Depends on: python3-lib2to3 (= 3.12.2-3ubuntu1.1) Installation candidate: 3.12.2-3ubuntu4 - https://packages.ubuntu.com/noble/python3-distutils dependency version pinned - https://packages.ubuntu.com/noble/python3-lib2to3 version not available - https://launchpad.net/ubuntu/noble/+package/python3-lib2to3 - https://launchpad.net/ubuntu/noble/+package/python3-distutils The published versions and their version requirements just don't match up. It seems no 'binary' distribution distutils is produced in noble: - https://launchpad.net/ubuntu/+source/python3-stdlib-extensions/ See 'Packages built by this source': - https://launchpad.net/ubuntu/+source/python3-stdlib-extensions/3.11.5-1 mantic has distutils - https://launchpad.net/ubuntu/+source/python3-stdlib-extensions/3.12.3-0ubuntu1 noble not - https://launchpad.net/ubuntu/+source/python3-stdlib-extensions/3.12.2-3ubuntu4 yet? Maybe this is because distutils is no longer part of the source package named in the package registry: - https://git.launchpad.net/ubuntu/+source/python3-stdlib-extensions/tree/3.11/Lib - https://git.launchpad.net/ubuntu/+source/python3-stdlib-extensions/tree/3.12/Lib It appears some refactoring is going on, or build errors persist, which might settle sooner or later. ** Affects: python3-stdlib-extensions (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/2061167 Title: python3-distutils is not built for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-stdlib-extensions/+bug/2061167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715749] Re: Intermittent black screen on HP EliteBook 840 G1
This bug still exists on Ubuntu 23.10. HP Elitebook 840 G1. inxi -Fxz System: Kernel: 6.5.0-21-generic arch: x86_64 bits: 64 compiler: N/A Desktop: GNOME v: 45.2 Distro: Ubuntu 23.10 (Mantic Minotaur) Machine: Type: Laptop System: Hewlett-Packard product: HP EliteBook 840 G1 v: A3009DD10303 serial: Mobo: Hewlett-Packard model: 198F v: KBC Version 15.59 serial: BIOS: Hewlett-Packard v: L71 Ver. 01.46 date: 07/20/2018 Battery: ID-1: BAT0 charge: 42.8 Wh (94.7%) condition: 45.2/45.2 Wh (100.0%) volts: 13.0 min: 11.4 model: Hewlett-Packard Primary status: charging CPU: Info: dual core model: Intel Core i5-4300U bits: 64 type: MT MCP arch: Haswell rev: 1 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 2622 high: 2708 min/max: 800/2900 cores: 1: 2594 2: 2594 3: 2594 4: 2708 bogomips: 19952 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel Haswell-ULT Integrated Graphics vendor: Hewlett-Packard driver: i915 v: kernel arch: Gen-7.5 bus-ID: 00:02.0 Device-2: Cheng Uei Precision Industry (Foxlink) HP HD Webcam driver: uvcvideo type: USB bus-ID: 2-7:3 Display: wayland server: X.Org v: 1.23.2 with: Xwayland v: 23.2.0 compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 resolution: 1280x720~60Hz API: OpenGL v: 4.6 Mesa 23.2.1-1ubuntu3.1 renderer: Mesa Intel HD Graphics 4400 (HSW GT2) direct-render: Yes Audio: Device-1: Intel Haswell-ULT HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus-ID: 00:03.0 Device-2: Intel 8 Series HD Audio vendor: Hewlett-Packard 8 driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 API: ALSA v: k6.5.0-21-generic status: kernel-api Server-1: PipeWire v: 0.3.79 status: active Network: Device-1: Intel Ethernet I218-LM vendor: Hewlett-Packard driver: e1000e v: kernel port: 3080 bus-ID: 00:19.0 IF: enp0s25 state: down mac: Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel bus-ID: 02:00.0 IF: wlo1 state: up mac: IF-ID-1: docker0 state: down mac: Bluetooth: Device-1: Intel Bluetooth wireless interface driver: btusb v: 0.8 type: USB bus-ID: 2-3.2:4 Report: hciconfig ID: hci0 rfk-id: 0 state: up address: bt-v: 4.0 lmp-v: 6 Drives: Local Storage: total: 119.24 GiB used: 72.01 GiB (60.4%) ID-1: /dev/sda vendor: Samsung model: MZ7PC128HAFU-000H1 size: 119.24 GiB Partition: ID-1: / size: 116.52 GiB used: 72.01 GiB (61.8%) fs: ext4 dev: /dev/sda4 Swap: ID-1: swap-1 type: file size: 4 GiB used: 127.2 MiB (3.1%) file: /swap.img Sensors: System Temperatures: cpu: 47.0 C mobo: N/A Fan Speeds (rpm): N/A Info: Processes: 268 Uptime: 2h 29m Memory: total: 8 GiB available: 7.65 GiB used: 5.26 GiB (68.8%) Init: systemd target: graphical (5) Compilers: gcc: 13.2.0 Packages: 2038 Shell: Bash v: 5.2.15 inxi: 3.3.29 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715749 Title: Intermittent black screen on HP EliteBook 840 G1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1715749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
The SMB1 code should be entirely removed from the stack. It’s insecure and deprecated everywhere. On Tue, May 2, 2023 at 8:56 AM BloodyIron <1828...@bugs.launchpad.net> wrote: > Upgraded to Ubuntu 23.04 and the issue persists... Will this ever get > fixed? This is now over 4 years old. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1881780). > https://bugs.launchpad.net/bugs/1828107 > > Title: > gvfs can't list shares from smb servers that disabled SMB1 > > Status in gvfs: > New > Status in gvfs package in Ubuntu: > Triaged > > Bug description: > After bug #1778322 is fixed (just needs a gvfs rebuild with newer > samba), samba machines will start to show up again in the "windows > network" tab in nautilus. But if a server has disabled the SMB1 > protocol, nautilus will show an error when that server is clicked on, > instead of showing the shares list. > > Even with SMB1 disabled, it should still be technically possible to > get a share list, since smbclient can do it: > > andreas@nsnx:~$ nmblookup -A 192.168.122.101 > Looking up status of 192.168.122.101 > D-NO-SMB1 <00> - B > D-NO-SMB1 <03> - B > D-NO-SMB1 <20> - B > ..__MSBROWSE__. <01> - B > WORKGROUP <00> - B > WORKGROUP <1d> - B > WORKGROUP <1e> - B > > MAC Address = 00-00-00-00-00-00 > > andreas@nsnx:~$ smbclient -L 192.168.122.101 -N > WARNING: The "syslog" option is deprecated > > Sharename Type Comment > - --- > print$ Disk Printer Drivers > pub_no_smb1 Disk > IPC$IPC IPC Service (d-no-smb1 server (Samba, > Ubuntu)) > Reconnecting with SMB1 for workgroup listing. > protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE > Failed to connect with SMB1 -- no workgroup available > > andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U > ubuntu%ubuntu -m NT1 > WARNING: The "syslog" option is deprecated > protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE > > andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U > ubuntu%ubuntu -m SMB2 > WARNING: The "syslog" option is deprecated > Try "help" to get a list of possible commands. > smb: \> dir > . D0 Fri May 3 18:16:38 > 2019 > .. D0 Fri May 3 18:15:24 > 2019 > hello.txt N 21 Fri May 3 18:16:12 > 2019 > hello-from-nsnx.txt A9 Fri May 3 18:16:38 > 2019 > > 20509264 blocks of size 1024. 13121800 blocks > available > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to a duplicate bug report (1881780). https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971427] Re: gdm in jammy defaults to wrong keymap option with no UI for fixing it
Yes, I can second the notion that this seems independent from the two proposed upstream issues, since this has also happened here when upgrading to 22.04. $ sudo cat /etc/default/keyboard XKBLAYOUT="de,us" XKBVARIANT="," BACKSPACE="guess" XKBMODEL="pc105" XKBOPTIONS="grp:alt_caps_toggle,grp_led:scroll" $ sudo cat /var/lib/AccountsService/users/yala [User] Session=ubuntu XSession=ubuntu Icon=/var/lib/AccountsService/icons/yala SystemAccount=false [InputSource0] xkb=de [InputSource1] xkb=us German (de) used to be the primary keymap on this system, but now English (en) is always preselected. This is a pretty nasty change in behaviour, as it blocks the boot up and login flow. jammy 5.15.0-33-generic gdm3 42.0-1ubuntu7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971427 Title: gdm in jammy defaults to wrong keymap option with no UI for fixing it To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1971427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972080] Re: GNOME (non-Ubuntu) login screen mouse cursor is a semi-opaque white square (missing adwaita-icon-theme-full)
Removal of the package 'sabily-gdm-themes' and rebooting had no effect on my situation. Daniel, perhaps you have some insight into this. What information I've found in my internet search says that gdm/gdm3 defaults to Adwaita icon theme. I'm looked for "how to configure" type articles about gdm and none have been applicable or have had not effect. Do you know how to reconfigure gdm in Ubuntu 22.04? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972080 Title: GNOME (non-Ubuntu) login screen mouse cursor is a semi-opaque white square (missing adwaita-icon-theme-full) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1972080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972080] Re: [mgag200] Mouse cursor is a semi-opaque white square (missing adwaita-icon-theme-full)
** Attachment added: "login screen WITH Adwaita/cursors" https://bugs.launchpad.net/ubuntu/+bug/1972080/+attachment/5588894/+files/login-screen-with-Adwaita-cursors.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972080 Title: [mgag200] Mouse cursor is a semi-opaque white square (missing adwaita- icon-theme-full) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1972080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972080] Re: [mgag200] Mouse cursor is a semi-opaque white square (missing adwaita-icon-theme-full)
** Attachment added: "login screen without Adwaita/cursors" https://bugs.launchpad.net/ubuntu/+bug/1972080/+attachment/5588893/+files/login-screen-without-Adwaita-cursors.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972080 Title: [mgag200] Mouse cursor is a semi-opaque white square (missing adwaita- icon-theme-full) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1972080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972080] Re: [mgag200] Mouse cursor is a semi-opaque white square (missing adwaita-icon-theme-full)
** Attachment added: "list of installed packages" https://bugs.launchpad.net/ubuntu/+bug/1972080/+attachment/5588892/+files/minis-packages.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972080 Title: [mgag200] Mouse cursor is a semi-opaque white square (missing adwaita- icon-theme-full) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1972080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972080] Re: [mgag200] Mouse cursor is a semi-opaque white square
Adding MUTTER_DEBUG_DISABLE_HW_CURSORS=1 to /etc/environment and rebooting had no effect on the issue. White square "mouse pointer" is present on gdm login screen if /usr/share/icons/adwaita/cursors is missing (renamed). If instead I install a symbolic link .../Adwaita/cursors -> .../Yaru/cursors and restart gdm I get valid mouse pointers. gdm is clearly looking for its cursor files in the Adwaita theme directory rather than Yaru. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972080 Title: [mgag200] Mouse cursor is a semi-opaque white square To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972080] Re: [mgag200] Mouse cursor is a semi-opaque white square
The reported problem is during login, not after successful login. I don't think mutter configuration has any effect before graphical login. Ubuntu's cursor theme may come from 'yaru-theme-icon', but does gdm's? Two files affect the observed condition: /usr/share/icons/Adwaita/cursors/left_ptr /usr/share/icons/Adwaita/cursors/xterm These come from the package 'adwaita-theme-icon-full'. If the package is not installed I have no login screen mouse pointer. Install the package and the pointer appears. Leave the package installed and deleted the two above files and the pointer is gone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972080 Title: [mgag200] Mouse cursor is a semi-opaque white square To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972080] Re: gdm has incomplete dependency
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+bug/1972080/+attachment/5587825/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972080 Title: gdm has incomplete dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1972080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972080] Re: gdm has incomplete dependency
** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+bug/1972080/+attachment/5587826/+files/lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972080 Title: gdm has incomplete dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1972080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re[2]: [Bug 1930925] Re: Ubuntu 20.04 doesn't work with a Manhattan 152785 KVM switch (but 18.04 does)
I tried Fedora 35, and found the exact same behaviour (ie the boot program recognises the keyboard, but the final linux image does not). Jon Thackray j...@pobox.com 0044 1223 276500 (home) 0044 7803 017991 (mobile) 0033 423354068 (France) -- Original Message -- From: "Jon Thackray" <1930...@bugs.launchpad.net> To: j...@pobox.com Sent: 22/04/2022 08:14:03 Subject: Re: [Bug 1930925] Re: Ubuntu 20.04 doesn't work with a Manhattan 152785 KVM switch (but 18.04 does) >Is there a set of builds between 19.04 and 19.10 that I could binary >chop through? This would allow a developer to narrow down where the bug >was introduced. Checking a build takes about half an hour, so if there >were say one per day between April 2019 and October 2019, that would >require 0.5 * log2 (180) hours, ie about 4 hours. > >Jon Thackray >j...@pobox.com > >0044 1223 276500 (home) >0044 7803 017991 (mobile) >0033 423354068 (France) > >-- Original Message -- >From: "Daniel van Vugt" <1930...@bugs.launchpad.net> >To: j...@pobox.com >Sent: 22/04/2022 03:00:03 >Subject: [Bug 1930925] Re: Ubuntu 20.04 doesn't work with a Manhattan >152785 KVM switch (but 18.04 does) > >>** Tags added: jammy >> >>-- >>You received this bug notification because you are subscribed to the bug >>report. >>https://bugs.launchpad.net/bugs/1930925 >> >>Title: >>Ubuntu 20.04 doesn't work with a Manhattan 152785 KVM switch (but >>18.04 does) >> >>Status in linux package in Ubuntu: >>Confirmed >> >>Bug description: >>I have recently acquired a acquired a desktop running ubuntu 20.04. I >>have several computers and switch between them using this KVM >>https://www.amazon.co.uk/gp/product/B077SV9MMQ/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8=1 >>The other machines are either running windows or ubuntu 18.04 or >>earlier. They are all fine, but the with 20.04 machine neither the >>keyboard nor the mouse works. On the 18.04 machine I can see >> >>lsusb >>Bus 002 Device 002: ID 8087:8000 Intel Corp. >>Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >>Bus 001 Device 002: ID 8087:8008 Intel Corp. >>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >>Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >>Bus 003 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver >>Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >> >>and it is the Logitech, Inc. Unifying Receiver which appears when the >>USB from the KVM is connected. On the 20.04 machine only this appears >> >>lsusb >>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >>Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED >> Controller >>Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub >>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >> >>I have tested installation discs from 19.04 onwards. The failure first >>appears in 19.10 and is still present in 21.04 >> >>I can observe a similar problem with a dual boot laptop running >>windows 10 and 20.04. With windows 10 I can use it with the KVM for >>screen and keyboard/mouse, but with ubuntu 20.04 the keyboard and >>mouse do not work. This issue has also been observed here >>https://unix.stackexchange.com/questions/646515/using-logitech-mouse- >>keyboard-on-tesmart-kvm-switch-with-ubuntu-20-04 and I have observed >>it using a Lindy 2 port HDMI/USB KVM (but I'm unsure of the model). >> >>I had to report this originally against xorg as this bug reporting >>system seems not to allow reporting of bugs against unknown packages. >>I also had to report it through the ubuntu-bug executable as I've been >>unable to find a way in launchpad of reporting a bug (as opposed to >>getting a guided tour about reporting bugs). >> >>I am happy to supply more info and test fixes if I am asked but as >>with this type of bug where something fails to happen rather than >>something wrong happens I don't know what to look at. >> >>ProblemType: Bug >>DistroRelease: Ubuntu 20.04 >>Package: xorg 1:7.7+19ubuntu14 >>ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 >>Uname: Linux 5.8.0-53-generic x86_64 >>ApportVersion: 2.20.11-0ubuntu27.18 >>Architecture: amd64 >>BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' >>CasperMD5CheckResult: skip >>
Re: [Bug 1930925] Re: Ubuntu 20.04 doesn't work with a Manhattan 152785 KVM switch (but 18.04 does)
Is there a set of builds between 19.04 and 19.10 that I could binary chop through? This would allow a developer to narrow down where the bug was introduced. Checking a build takes about half an hour, so if there were say one per day between April 2019 and October 2019, that would require 0.5 * log2 (180) hours, ie about 4 hours. Jon Thackray j...@pobox.com 0044 1223 276500 (home) 0044 7803 017991 (mobile) 0033 423354068 (France) -- Original Message -- From: "Daniel van Vugt" <1930...@bugs.launchpad.net> To: j...@pobox.com Sent: 22/04/2022 03:00:03 Subject: [Bug 1930925] Re: Ubuntu 20.04 doesn't work with a Manhattan 152785 KVM switch (but 18.04 does) >** Tags added: jammy > >-- >You received this bug notification because you are subscribed to the bug >report. >https://bugs.launchpad.net/bugs/1930925 > >Title: > Ubuntu 20.04 doesn't work with a Manhattan 152785 KVM switch (but > 18.04 does) > >Status in linux package in Ubuntu: > Confirmed > >Bug description: > I have recently acquired a acquired a desktop running ubuntu 20.04. I > have several computers and switch between them using this KVM >https://www.amazon.co.uk/gp/product/B077SV9MMQ/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8=1 > The other machines are either running windows or ubuntu 18.04 or > earlier. They are all fine, but the with 20.04 machine neither the > keyboard nor the mouse works. On the 18.04 machine I can see > > lsusb > Bus 002 Device 002: ID 8087:8000 Intel Corp. > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 001 Device 002: ID 8087:8008 Intel Corp. > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 003 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver > Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > and it is the Logitech, Inc. Unifying Receiver which appears when the > USB from the KVM is connected. On the 20.04 machine only this appears > > lsusb > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller > Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > I have tested installation discs from 19.04 onwards. The failure first > appears in 19.10 and is still present in 21.04 > > I can observe a similar problem with a dual boot laptop running > windows 10 and 20.04. With windows 10 I can use it with the KVM for > screen and keyboard/mouse, but with ubuntu 20.04 the keyboard and > mouse do not work. This issue has also been observed here >https://unix.stackexchange.com/questions/646515/using-logitech-mouse- > keyboard-on-tesmart-kvm-switch-with-ubuntu-20-04 and I have observed > it using a Lindy 2 port HDMI/USB KVM (but I'm unsure of the model). > > I had to report this originally against xorg as this bug reporting > system seems not to allow reporting of bugs against unknown packages. > I also had to report it through the ubuntu-bug executable as I've been > unable to find a way in launchpad of reporting a bug (as opposed to > getting a guided tour about reporting bugs). > > I am happy to supply more info and test fixes if I am asked but as > with this type of bug where something fails to happen rather than > something wrong happens I don't know what to look at. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 > Uname: Linux 5.8.0-53-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > Date: Fri Jun 4 20:21:15 2021 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > DpkgLog: > > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA controller]) > Subsystem: ASUSTeK Computer Inc. Device [1043:8694] > InstallationDate: Installed on 2021-05-14 (21 days ago) > InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 > (20210209.1) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller >Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Lsusb-t: >/: Bus 02.Port 1: Dev 1,
Re: [Bug 1930925] Re: Ubuntu 20.04 doesn't work with a Manhattan 152785 KVM switch (but 18.04 does)
I just tried Ubuntu 22.04. Whilst the installer works correctly with the KVM (so I can for example choose option 1, try or install), the installation doesn't work (at least, not with the mouse, and without that I can't get anything that would be sensitive to the keyboard). By this time next year, there will be no Ubuntu (or Debian I think, given that Rapsbian doesn't work with the KVM either) distribution I can use, as at that point 18.04 will be end of support. I shall then start having to try and learn other distros to see if any of them have fixed/failed to create this bug. Jon Thackray j...@pobox.com 0044 1223 276500 (home) 0044 7803 017991 (mobile) 0033 423354068 (France) -- Original Message -- From: "Launchpad Bug Tracker" <1930...@bugs.launchpad.net> To: j...@pobox.com Sent: 03/08/2021 04:57:57 Subject: [Bug 1930925] Re: Ubuntu 20.04 doesn't work with a Manhattan 152785 KVM switch (but 18.04 does) >Status changed to 'Confirmed' because the bug affects multiple users. > >** Changed in: linux (Ubuntu) >Status: New => Confirmed > >-- >You received this bug notification because you are subscribed to the bug >report. >https://bugs.launchpad.net/bugs/1930925 > >Title: > Ubuntu 20.04 doesn't work with a Manhattan 152785 KVM switch (but > 18.04 does) > >Status in linux package in Ubuntu: > Confirmed > >Bug description: > I have recently acquired a acquired a desktop running ubuntu 20.04. I > have several computers and switch between them using this KVM >https://www.amazon.co.uk/gp/product/B077SV9MMQ/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8=1 > The other machines are either running windows or ubuntu 18.04 or > earlier. They are all fine, but the with 20.04 machine neither the > keyboard nor the mouse works. On the 18.04 machine I can see > > lsusb > Bus 002 Device 002: ID 8087:8000 Intel Corp. > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 001 Device 002: ID 8087:8008 Intel Corp. > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 003 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver > Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > and it is the Logitech, Inc. Unifying Receiver which appears when the > USB from the KVM is connected. On the 20.04 machine only this appears > > lsusb > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller > Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > I have tested installation discs from 19.04 onwards. The failure first > appears in 19.10 and is still present in 21.04 > > I can observe a similar problem with a dual boot laptop running > windows 10 and 20.04. With windows 10 I can use it with the KVM for > screen and keyboard/mouse, but with ubuntu 20.04 the keyboard and > mouse do not work. This issue has also been observed here >https://unix.stackexchange.com/questions/646515/using-logitech-mouse- > keyboard-on-tesmart-kvm-switch-with-ubuntu-20-04 and I have observed > it using a Lindy 2 port HDMI/USB KVM (but I'm unsure of the model). > > I had to report this originally against xorg as this bug reporting > system seems not to allow reporting of bugs against unknown packages. > I also had to report it through the ubuntu-bug executable as I've been > unable to find a way in launchpad of reporting a bug (as opposed to > getting a guided tour about reporting bugs). > > I am happy to supply more info and test fixes if I am asked but as > with this type of bug where something fails to happen rather than > something wrong happens I don't know what to look at. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 > Uname: Linux 5.8.0-53-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > Date: Fri Jun 4 20:21:15 2021 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > DpkgLog: > > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA controller]) > Subsystem: ASUSTeK Computer Inc. Device [1043:8694] > InstallationDate: Installed on 2021-05-14 (21 days ago) > InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release a
[Bug 1969636] [NEW] goverlay immediately errors out on jammy beta
Public bug reported: goverlay does not display its window and immediately exits, with the following error if run from terminal: can't get libdl.so Tested on jammy beta, up to date as of 2022-04-20 1500 UTC. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: goverlay 0.7.1-2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 10:18:46 2022 InstallationDate: Installed on 2022-04-19 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: goverlay UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: goverlay (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy 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/1969636 Title: goverlay immediately errors out on jammy beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/goverlay/+bug/1969636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957924] Re: rpc-worker: debugfs access is restricted
From libvirt gitlib... Daniel P. Berrangé @berrange · 2 months ago Owner The QEMU patches required to solve this are here https://lists.gnu.org/archive/html/qemu-devel/2022-02/msg03279.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957924 Title: rpc-worker: debugfs access is restricted To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/1957924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798166] Re: “Mouse battery low” notification can't be disabled
I'm using Ubuntu 20.04.4 LTS and GNOME 3.36.8 Still having this problem. Very surprised it has lasted this long. In any case, if it is fixed, will this change make it to the next LTS update? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798166 Title: “Mouse battery low” notification can't be disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961473] [NEW] crashed when I tried a clean install of Xubuntu 20.04
Public bug reported: I don't really know what happened. 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 CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail CasperVersion: 1.445 Date: Sat Feb 19 05:52:07 2022 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: ubiquity UbiquitySyslog: UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal xubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961473 Title: crashed when I tried a clean install of Xubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1961473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950780] Re: Thunderbolt dock usb ports not working
I am also adding the output from boltctl, if you need any other info please advise. ** Attachment added: "Boltctl output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950780/+attachment/5540412/+files/boltctl.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950780 Title: Thunderbolt dock usb ports not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950780] Re: Thunderbolt dock usb ports not working
Adding dmesg output from computer ** Attachment added: "Output from dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950780/+attachment/5540411/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950780 Title: Thunderbolt dock usb ports not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950780] [NEW] Thunderbolt dock usb ports not working
Public bug reported: I have a Lenovo Thunderbolt 3 Gen 2 dock and wanted to use this with Ubuntu 21.10. When booting an unmodified version the usb ports do not work. After an inspection with journalctl I find the error message "No bus number available for hot-added bridge" and a google search led me to this workaround: Add pci=realloc,assign-busses,hpbussize=0x33. This line as a boot parameter makes the dock work as intended. I believe this should be fixed so that people using the live image can see that their hardware works as intended before installing. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: dock kernel thunderbolt ** Attachment added: "Output from lspci" https://bugs.launchpad.net/bugs/1950780/+attachment/5540410/+files/lspci.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950780 Title: Thunderbolt dock usb ports not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946532] [NEW] package ubuntu-advantage-tools 27.2.2~18.04.1 failed to install/upgrade: installed ubuntu-advantage-tools package post-installation script subprocess returned error exit status 1
Public bug reported: Doing a dist-upgrade from 18.04 to 20.04: Errors were encountered while processing: ubuntu-advantage-tools Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (294.9 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ./usr/lib/python3/dist-packages/requests/__init__.py:80: RequestsDependencyWarning: urllib3 (1.26.2) or chardet (3.0.4) doesn't match a supported version! RequestsDependencyWarning) .. *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 99% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage- tools/+filebug/5979f17e-2883-11ec-a1ce-d485646cd9a4?field.title=package+ubuntu- advantage- tools+27.2.2%7E18.04.1+failed+to+install%2Fupgrade%3A+installed+ubuntu- advantage-tools+package+post- installation+script+subprocess+returned+error+exit+status+1 You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ubuntu-advantage-tools 27.2.2~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-159.167-generic 4.15.18 Uname: Linux 4.15.0-159-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.26 Architecture: amd64 Date: Fri Oct 8 17:59:57 2021 ErrorMessage: installed ubuntu-advantage-tools package post-installation script subprocess returned error exit status 1 Python3Details: /opt/anaconda3/bin/python3.7, Python 3.7.6, unpackaged PythonDetails: /opt/anaconda3/bin/python3.7, Python 3.7.6, unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.14 SourcePackage: ubuntu-advantage-tools Title: package ubuntu-advantage-tools 27.2.2~18.04.1 failed to install/upgrade: installed ubuntu-advantage-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2021-10-08 (0 days ago) ** Affects: ubuntu-advantage-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic need-duplicate-check third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946532 Title: package ubuntu-advantage-tools 27.2.2~18.04.1 failed to install/upgrade: installed ubuntu-advantage-tools package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1946532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937897] Re: GPIO error logs in start and dmesg after update of kernel
Confirmed! Finally. With the latest HWE: $ apt show linux-image-5.11.0-37-generic Package: linux-image-5.11.0-37-generic Version: 5.11.0-37.41~20.04.2 ... No errors or warnings in dmesg or journalctl -b seen on my statem anymore. Motherboard: ASUS PRIME X570-PRO (latest BIOS v 4021) CPU: Ryzen 9 3950X Other HW shouldn't matter I guess. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937897 Title: GPIO error logs in start and dmesg after update of kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937897] Re: GPIO error logs in start and dmesg after update of kernel
Confirmed. Just updated and same. Can you backport the fix to the 20.04 HWE kernel? I mean that's the one Canonical recommends has as first choice if downloading Ubuntu from ubuntu.com, for years now. And they've become more stable in my experience than the ones between LTS versions, which is good. The others should be more testing grounds and those who can live with having to fix possibly basic stuff. And definitely more common nowadays that third party software outside repos (incl. PPAs), proprietary or not, often lists only the latest or two latest LTS versions as supported and downloads (repo or deb package). Tried Ubuntu 21.04 some months ago, just to see if something new cool stuff, in a VM (IIRC, or it was a USB stick) and well let's say KVM+QEMU or my PC, me either, didn't like it. Boot warnings, even red errors from systemd on a clean updated install, and several (official) packages that are in the repos didn't even launch, some DKMS modules failed... Can't use that as a primary workstation + server. With snaps etc you can run pretty bleeding edge both desktop and CLI stuff like certbot (Let's Encrypt) on 20.04, so. Snaps use an 18.04 core - makes sense for compatibility. Doesn't stop you from the latest Blender version or whatever. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937897 Title: GPIO error logs in start and dmesg after update of kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937897] Re: GPIO error logs in start and dmesg after update of kernel
And will that kernel come to the Ubuntu 20.04 LTS HWE stack, say in 20.04.4? Kinda need to use LTS versions, us that need that stability at least. Not really interested in fixes for 21.10 or something... Focal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937897 Title: GPIO error logs in start and dmesg after update of kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937897] Re: GPIO error logs in start and dmesg after update of kernel
To be clear this issue started with Kernel 5.8.0-63 NOT 5.11 (on Focal / 20.04 HWE LTS) Well Ubuntu Kernel Bot, that's exactly what I did in comment #14 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937897/comments/14 Latest 5.13 kernel in -prosed on Focal (20.04.3) gets the same gpio errors and warnings in dmesg and "journalctl -b" as with the current 5.11 HWE kernel. X570 Motherboard Ryzen 9 3950X Zen2 CPU Same error appears twice during boot. Here's the output from "journalctl -b" --- sep. 12 15:37:43 tux kernel: gpio gpiochip1: (gpio_aaeon): tried to insert a GPIO chip with zero lines sep. 12 15:37:43 tux kernel: gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22 sep. 12 15:37:43 tux kernel: gpio-aaeon: probe of gpio-aaeon.0 failed with error -22 sep. 12 15:37:44 tux kernel: gpio gpiochip1: (gpio_aaeon): tried to insert a GPIO chip with zero lines sep. 12 15:37:44 tux kernel: gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22 sep. 12 15:37:44 tux kernel: gpio-aaeon: probe of gpio-aaeon.0 failed with error -22 --- They're both "gpiochip1 - GPIOs 0..-1", so why try again right after the first fails? Does NOT appear on my Intel NUC Core i3. It's a 2013 model but runs the exact same kernel at least. Likely not on any Intel based motherboards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937897 Title: GPIO error logs in start and dmesg after update of kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937897] Re: GPIO error logs in start and dmesg after update of kernel
** Tags removed: verification-needed-focal ** Tags added: verification-failed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937897 Title: GPIO error logs in start and dmesg after update of kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937897] Re: GPIO error logs in start and dmesg after update of kernel
Added tag 'verification-failed-hirsute'. Enabled proposed and installed package 'linux-image-5.13.0-14-generic' version '5.13.0-14.14~20.04.4' on my 20.04.3 LTS, and still get in dmesg: [1.228729] gpio gpiochip1: (gpio_aaeon): tried to insert a GPIO chip with zero lines [1.228732] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22 [1.228735] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22 [7.238390] gpio gpiochip1: (gpio_aaeon): tried to insert a GPIO chip with zero lines [7.238396] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22 [7.238401] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22 ** Tags removed: verification-needed-hirsute ** Tags added: verification-failed-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937897 Title: GPIO error logs in start and dmesg after update of kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929504] Re: Add support for IO functions of AAEON devices
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929504 Title: Add support for IO functions of AAEON devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925974] Re: Ubuntu 21.04 (Hirsute) MOTD network section is broken
Hi,
The latest file shows as follows:
```
try:
fcntl.ioctl(sock, SIOCETHTOOL, packed) # Status ioctl() call
if _PY3:
res = status_cmd.tobytes()
else:
res = status_cmd.tostring()
speed, duplex = struct.unpack("12xHB28x", res)
```
However even with this, or replacing and forcing only tobytes() still produces
the following for us:
2021-08-18 03:13:20,074 ERRORNetwork plugin raised an exception.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/landscape/sysinfo/sysinfo.py", line 99,
in run
result = plugin.run()
File "/usr/lib/python3/dist-packages/landscape/sysinfo/network.py", line 36,
in run
device_info = self._get_device_info()
File "/usr/lib/python3/dist-packages/landscape/lib/network.py", line 158, in
get_active_device_info
flags = get_flags(sock, interface.encode())
File "/usr/lib/python3/dist-packages/landscape/lib/network.py", line 136, in
get_flags
data = fcntl.ioctl(
OSError: [Errno 19] No such device
We have some our ip link has various dummy interfaces and some vrf info
in it. not sure if that would cause issues with this or not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925974
Title:
Ubuntu 21.04 (Hirsute) MOTD network section is broken
To manage notifications about this bug go to:
https://bugs.launchpad.net/landscape-client/+bug/1925974/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929504] Re: Add support for IO functions of AAEON devices
OK, but don't try to load the gpio-aaeon module on PCs that, if simply one tries to load it manually, it simply says that no such device exists... It shows twice in the boot log (dmesg + journalctl -b) but even worse also on the monitors, although GRUB has "quiet" specified (no splash). Worst of all, on my Ryzen 3950X (16C/32T) with 5.5 GB/s PCIe4 NVMes you get used to 1-2 second boot speed. But this actually reduces it significantly compared to that. However it seems to be faster now that the 5.11 kernel is the HWE one. The last 5.8 one introduced this bug for me. https://bugs.launchpad.net/bugs/1937897 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929504 Title: Add support for IO functions of AAEON devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937897] Re: GPIO error logs in start and dmesg after update of kernel
Well OK there is a module with that name, however I did blacklist it and same error still occurs. It happens very early in the boot process. Now maybe it tries to load gpio-aaeon, but still early to load modules I would say, it's still doing say GRUB kernel parameters like fsck ones. Now I have confirmed it does slow down boot pretty badly, however the HWE stack just got kernel 5.11 and although it has the same error it does seem to *almost* boot as fast as without any error. Now I tried to actually load that module, so the reverse. It simply says that no such device exists. Conclusion/TLDR: So it shouldn't try to load it in the first place. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937897 Title: GPIO error logs in start and dmesg after update of kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811724] Re: libbd_mdraid.so.2: cannot open shared object file
Same on Ubuntu 20.04 both GA and HWE kernel. Sure, it just takes this command to find which package has it: $ apt-file search libbd_mdraid.so.2 And get "libblockdev-mdraid2", which does "fix" it, but I DON'T need it. Depends on packages I don't need, MOST don't need: $ apt show libblockdev-mdraid2 Depends: libblockdev-utils2 (>= 2.20), libbytesize1 (>= 2.1), libc6 (>= 2.27), libglib2.0-0 (>= 2.42.2), mdadm (>= 3.3.2) However it's the same on Raspbian for the Raspberry Pi, so it's more of a Debian problem. And installing that package then wants exim4 and all... A mail server?? For a library? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811724 Title: libbd_mdraid.so.2: cannot open shared object file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1811724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937897] Re: GPIO error logs in start and dmesg after update of kernel
No, I can't, because there isn't a single module loaded with even the name "gpio" in it. So running: $ lsmod|grep gpio == No result It's in the kernel, not a module. I reverted to the GA kernel and although with that I've had some issue with on headless *Intel* NUC running Virtual Machines that use the more optimized Ubuntu KVM kernel, using libvirt (host uses the latest HWE), where both host and VMs slow down to a crawl randomly without errors. But on my Ryzen 9 workstation the GA kernel is super stable, fast and just works. A little slower in Vulkan *Benchmarks*, that's basically it. And yes, it runs a bunch of server services. Mainly does that like "22/7", for LAN and WAN. Biggest "drawback" is that the 5.4 kernel's k10temp module does not display the temperatures of my Corsair PCIe4 5.5 GB/s NVMEs (just running "sensors"), but well that doesn't matter. I've stressed them well enough before, to see that my cooling is absolutely enough (and they come with a built-in heatsink. Sure I could've reverted to the previous 5.8 kernel, but it's tied to HWE (metapackages), unless I uninstall them, and then, well no security updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937897 Title: GPIO error logs in start and dmesg after update of kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937897] Re: GPIO error logs in start and dmesg aftzer update of kernel
EDIT: To clarify both times these lines come they refer to "gpiochip1"
(so not 2 different ones).
I started getting the same 3 lines of errors TWICE at boot, with the now
latest official 5.8 HWE kernel. Without "splash", just "quiet" set for
GRUB it also shows on my monitors when booting. Honestly seems to slow
down boot too (I mean I have 5.5 GB/s R/W NVMes and it can get to GDM in
maybe less than 2 seconds).
WHAT HAPPENED:
After my 20.04.2 (HWE) kernel was updated From:
linux-image-5.8.0-59-generic
To:
linux-image-5.8.0-63-generic
If I boot the former (*-59) or any older, I don't see the below errors
TWICE. With the latter (*-63) I do. Seems to be little to none
information about this. I only find it in the Linux source code. Is it
something new in Linux?
Running journalctl -b (now) first 3 lines of errors come after early
kernel NVME(s) preparation, but have just checked that once (now). Seems
random as the next exact same 3 lines come below something completely
different in the log. But again system can boot in 2 secs, however seems
slower with these in fact.
$ journalctl -b
RED LINES:
kernel: gpio gpiochip1: (gpio_aaeon): tried to insert a GPIO chip with zero
lines
gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22
YELLOW LINE:
gpio-aaeon: probe of gpio-aaeon.0 failed with error -22
... and again later in the log:
RED LINES:
kernel: gpio gpiochip1: (gpio_aaeon): tried to insert a GPIO chip with zero
lines
gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22
YELLOW LINE:
gpio-aaeon: probe of gpio-aaeon.0 failed with error -22
---
Apart from that everything works. No new hardware has been added.
Pretty generic system (hefty CPU but still X570 + Zen2):
* ASUS X570 AM4 Motherboard ("Prime Pro")
* Ryzen Zen2 3950X 16C/32T CPU
* ASUS Radeon RX 5500 XT 8 GB OC GPU
* 2 NVMes and 3 HDDs (total 12 TB)
* No special peripherals
Happens really early at boot, so seems low-level.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937897
Title:
GPIO error logs in start and dmesg aftzer update of kernel
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937897/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936243] [NEW] Initial Installation
Public bug reported: After running a fresh installation the app crashed. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.19 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 14 12:34:30 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 RebootRequiredPkgs: linux-image-5.11.0-16-generic linux-base SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubiquity-21.04.19 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936243 Title: Initial Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1936243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909805] Re: libclc-amdgcn missing files for current AMD APUs
Same problem too with Radeon RX 5500 XT. It worked on my Radeon RX 570 (AMD X570 + Ryzen 3950X). Using the generic ICD and Mesa OpenCL doesn't work. The easy fix that also gives better results on all benchmarks I've done for Vulkan and OpenGL is installing the latest AMDGPU Pro driver (version 21.20) from AMD.com. Remember to specify: --opencl=rocr It's Open Source as most AMD projects. https://github.com/RadeonOpenCompute/ROCm So NVIDIA users can use most of AMD's stuff because of being FOSS, like the below mentioned FidelityFX, is Open Source and appears for NVIDIA users too in the growing number of games supporting it. NVIDIA however contribute little back... PS: Previously it was --opencl=PAL but that is deprecated. The installation docs and script help are updated good and now finally tells what legacy is (older than Vega 10). Using --help on the installation script tells what you need. Basically just that you specify (IDK what it does if you don't specify an OpenCL type but you can check with --dry- run and see if it installs packages with "rocr", the new, or "orca", the old. If you use the pro installation script, it is the same as specifying --pro on the all-free unless pro is specified. Adding legacy OpenCL as well is NO point, as shown as an example in the docs, only if you switch between this and older than Vega 10 cards, as that legacy loader doesn't work alone, but doesn't matter if it's installed, however say Geekbench will complain about a lacking library (.so). Legacy for older than Vega 10 AMD Support told me before they added it to the docs. Supports Ubuntu 20.04.2 and Ubuntu 18.04.5. Made the mistake of installing the previous that said Ubuntu 20.04.1 while having 20.04.2, as I supposed it wouldn't matter, as I've never had problems before. However, didn't work. Then of course like days later they had released one with "initial support" (because 1 known issue but rare use case), then soon after the current with a fix for that. As soon as installed, as it uses DKMS, I'm sure say when 20.04.3 comes it'll just work. Driver uses a local apt repo so must be manually updated (which is good if you're very satisfied with the one you've got now). Keep in mind apparently there will be a new driver with some good updates to FidelityFX etc, although that already works in the 21.10 driver (Shadow of The Tomb Raider for example). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909805 Title: libclc-amdgcn missing files for current AMD APUs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1909805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934160] Re: Include path picker wants a file instead of a folder
Did some more testing: - Issue does not happen when launching frescobaldi with sudo, but the setting does not apply to normal user - Issue does not happen in GNOME (tested with Ubuntu 21.04) - workaround: add line to ~/.config/frescobaldi/frescobaldi.conf in the [lilypond_settings] section- include_path=/home/ubuntu/Downloads, /home/ubuntu/Music -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934160 Title: Include path picker wants a file instead of a folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/frescobaldi/+bug/1934160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934160] [NEW] Include path picker wants a file instead of a folder
Public bug reported: I'm on Ubuntu Studio 21.04 with KDE Plasma 5.21.4 and Frescobaldi 3.1.3 from the repos. When I go to the Preferences, under Lilypond Preferences, I tried to add a folder to the include path. When I click Add, the dialog seems to be looking for a file rather than a folder. The heading of the dialog says Open File, and it won't let me click Open in any folder. No files show up within my folders in the dialog even the Filter is set to All Files. It should let me choose a folder to add to the include list. ** Affects: frescobaldi (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/1934160 Title: Include path picker wants a file instead of a folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/frescobaldi/+bug/1934160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933782] [NEW] Needs updating
Public bug reported: The most recent version of this program is 3.6.2 and contains significant improvements in engraving, including new fonts. https://musescore.org/en/node/317195 ** Affects: musescore3 (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/1933782 Title: Needs updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/musescore3/+bug/1933782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933550] [NEW] libapache2-mod-shib2: Installation fails because of unmet dependencies
Public bug reported: Dear Maintainers, I'm seeing the following error when trying to install the libapache2 -mod-shib2 package. This causes the package to fail to install. ``` $ sudo apt install libapache2-mod-shib2 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libapache2-mod-shib2 : Depends: libshibsp-plugins (= 2.6.1+dfsg1-2) but it is not going to be installed Depends: shibboleth-sp2-utils (>= 2.6) but it is not going to be installed Depends: libshibsp7 but it is not going to be installed Depends: libxmltooling7 (>= 1.6.0-5) but it is not going to be installed E: Unable to correct problems, you have held broken packages. ``` There are no "held broken packages" on this system. System information: ``` $ lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 ``` Package information: ``` $ apt-cache policy libapache2-mod-shib2 libapache2-mod-shib2: Installed: (none) Candidate: 2.6.1+dfsg1-2 Version table: 2.6.1+dfsg1-2 500 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 2.5.3+dfsg-2.1build1 -1 100 /var/lib/dpkg/status ``` This error seems identical to an error reported for Debian Sid in 2018 (see link below). https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909558 Best, Jon Green ** Affects: shibboleth-sp2 (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/1933550 Title: libapache2-mod-shib2: Installation fails because of unmet dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shibboleth-sp2/+bug/1933550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1930925] Re: Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM switch
I don't have a "Unifying receiver". That's just the name which appears and/or disappears when I plug in the KVM to the PC. The KVM in all cases is directly connected to the keyboard/mouse/screen at one end, and USB ports/HDMI at the PC end. -- Original Message -- From: "Hui Wang" <1930...@bugs.launchpad.net> To: j...@pobox.com Sent: 08/06/2021 11:21:35 Subject: [Bug 1930925] Re: Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM switch >Please plug the Unifying Receiver to the usb port of 20.04 machine >directly (the usb port which connects to the KVM switch), then run lsusb >and upload the output. > >Let us compare the log with the one you plug the Unifying Receiver to >the usb port of KVM switch. > >-- >You received this bug notification because you are subscribed to the bug >report. >https://bugs.launchpad.net/bugs/1930925 > >Title: > Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a > KVM switch > >Status in linux package in Ubuntu: > New > >Bug description: > I have recently acquired a acquired a desktop running ubuntu 20.04. I > have several computers and switch between them using this KVM >https://www.amazon.co.uk/gp/product/B077SV9MMQ/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8=1 > The other machines are either running windows or ubuntu 18.04 or > earlier. They are all fine, but the with 20.04 machine neither the > keyboard nor the mouse works. On the 18.04 machine I can see > > lsusb > Bus 002 Device 002: ID 8087:8000 Intel Corp. > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 001 Device 002: ID 8087:8008 Intel Corp. > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 003 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver > Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > and it is the Logitech, Inc. Unifying Receiver which appears when the > USB from the KVM is connected. On the 20.04 machine only this appears > > lsusb > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller > Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > I have tested installation discs from 19.04 onwards. The failure first > appears in 19.10 and is still present in 21.04 > > I can observe a similar problem with a dual boot laptop running > windows 10 and 20.04. With windows 10 I can use it with the KVM for > screen and keyboard/mouse, but with ubuntu 20.04 the keyboard and > mouse do not work. This issue has also been observed here >https://unix.stackexchange.com/questions/646515/using-logitech-mouse- > keyboard-on-tesmart-kvm-switch-with-ubuntu-20-04 and I have observed > it using a Lindy 2 port HDMI/USB KVM (but I'm unsure of the model). > > I had to report this originally against xorg as this bug reporting > system seems not to allow reporting of bugs against unknown packages. > I also had to report it through the ubuntu-bug executable as I've been > unable to find a way in launchpad of reporting a bug (as opposed to > getting a guided tour about reporting bugs). > > I am happy to supply more info and test fixes if I am asked but as > with this type of bug where something fails to happen rather than > something wrong happens I don't know what to look at. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 > Uname: Linux 5.8.0-53-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > Date: Fri Jun 4 20:21:15 2021 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > DpkgLog: > > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA controller]) > Subsystem: ASUSTeK Computer Inc. Device [1043:8694] > InstallationDate: Installed on 2021-05-14 (21 days ago) > InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 > (20210209.1) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller >Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Lsusb-t: >/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M >/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M >|__ Port 11: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M >|__ Port 13: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
Re: [Bug 1930925] Re: Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM switch
Neither. I tested all the distros on an old machine I have which currently runs windows 10. The distros were tested by putting the installation on a DVD and booting from it. Here's what windows claims it has Device namefeit ProcessorIntel(R) Core(TM) i7-2700K CPU @ 3.50GHz 3.50 GHz Installed RAM16.0 GB Device ID86452CEC-D6C1-46A6-9970-7FE2338F4B02 Product ID00326-1-0-AA334 System type64-bit operating system, x64-based processor Pen and touchNo pen or touch input is available for this display Here's the motherboard info C:\Users\Jon>wmic baseboard get product,Manufacturer,version,serialnumber Manufacturer Product SerialNumber Version Intel Corporation DH67BL BTBL13400AKJ AAG10189-209 I can't find an easy way to copy the USB info, so here's a screenshot (attached) -- Original Message -- From: "Hui Wang" <1930...@bugs.launchpad.net> To: j...@pobox.com Sent: 08/06/2021 11:24:28 Subject: [Bug 1930925] Re: Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM switch >BTW, you said you tested 19.10 and onwards, did you test them on that >20.04 machine (ASuS machine) or the 18.04 machine? > >-- >You received this bug notification because you are subscribed to the bug >report. >https://bugs.launchpad.net/bugs/1930925 > >Title: > Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a > KVM switch > >Status in linux package in Ubuntu: > New > >Bug description: > I have recently acquired a acquired a desktop running ubuntu 20.04. I > have several computers and switch between them using this KVM >https://www.amazon.co.uk/gp/product/B077SV9MMQ/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8=1 > The other machines are either running windows or ubuntu 18.04 or > earlier. They are all fine, but the with 20.04 machine neither the > keyboard nor the mouse works. On the 18.04 machine I can see > > lsusb > Bus 002 Device 002: ID 8087:8000 Intel Corp. > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 001 Device 002: ID 8087:8008 Intel Corp. > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 003 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver > Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > and it is the Logitech, Inc. Unifying Receiver which appears when the > USB from the KVM is connected. On the 20.04 machine only this appears > > lsusb > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller > Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > I have tested installation discs from 19.04 onwards. The failure first > appears in 19.10 and is still present in 21.04 > > I can observe a similar problem with a dual boot laptop running > windows 10 and 20.04. With windows 10 I can use it with the KVM for > screen and keyboard/mouse, but with ubuntu 20.04 the keyboard and > mouse do not work. This issue has also been observed here >https://unix.stackexchange.com/questions/646515/using-logitech-mouse- > keyboard-on-tesmart-kvm-switch-with-ubuntu-20-04 and I have observed > it using a Lindy 2 port HDMI/USB KVM (but I'm unsure of the model). > > I had to report this originally against xorg as this bug reporting > system seems not to allow reporting of bugs against unknown packages. > I also had to report it through the ubuntu-bug executable as I've been > unable to find a way in launchpad of reporting a bug (as opposed to > getting a guided tour about reporting bugs). > > I am happy to supply more info and test fixes if I am asked but as > with this type of bug where something fails to happen rather than > something wrong happens I don't know what to look at. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 > Uname: Linux 5.8.0-53-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > Date: Fri Jun 4 20:21:15 2021 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > DpkgLog: > > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA controller]) > Subsystem: ASUSTeK Computer Inc. Device [1043:8694] > InstallationDate: Installe
[Bug 1930640] Re: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object
Confirmed everything appears to be working. We can consider this closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930640 Title: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1930640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930640] Re: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object
After a little more digging, I believe part of my issue with the boto3+s3 option was that I was still using the full URL rather than just the bucket name, so rather than: boto3+s3://BUCKET_NAME/folder I was still using: boto3+s3://s3-us-west-2.amazonaws.com/BUCKET_NAME/folder So this appears to be working and I'm seeing files show up in S3 and nothing has produced an error so far after six hours (and counting) of backing up. Although it's still weird that the old S3 URL of s3://s3-us- west-2.amazonaws.com/BUCKET_NAME/folder that works in the 0.7.19 version of Duplicity with Python 2.7 was able to use the old S3 URL, but the new one on 0.8.19 (and 0.8.11) didn't seem to jive with it. But since the boto3+s3://bucket_name works with the multipart chunking, I'll just stick with this instead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930640 Title: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1930640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930640] Re: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object
No funny characters in the bucket name. It's literally just alpha characters and dashes: labkey-artifactory- backup And the folder it drops into uses an underscore: artifactory_backup I'll recheck that link. There were a few that I already saw, but were not applicable to my situation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930640 Title: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1930640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930640] Re: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object
I've tried using boto3+s3:// as well before and it was unsuccessful. Swapping it out with this newer version of duplicity produced an error regarding the HeadBucket operation. See new failure below. I turned up the verbosity to 9 for this one. Note: My company is using Duplicity 0.8.11 and Duply in other servers (Servers are running Ubuntu 20.04 w/Python 3.5.8) without issue. However, this particular machine is the only one where we needed to implement multipart chunks due to the size of the backup being so huge compared to our other servers that don't need it. I know that on a different server (Ubuntu 16.04) running Duplicity 0.7.19 on Python 2.7, the multipart chunking worked without issue, but since we can't run that version of Python or Duplicity on this newer version of Ubuntu, I'm not sure what else we need to do to get 0.8.19 to work here. Start duply v2.2, time is 2021-06-04 21:26:37. Using profile '/root/.duply/artifactory_backup'. Using installed duplicity version 0.8.19, python 3.8.5 (/usr/bin/python3), gpg 2.2.19 (Home: /root/.gnupg), awk 'GNU Awk 5.0.1, API: 2.0 (GNU MPFR 4.0.2, GNU MP 6.2.0)', grep 'grep (GNU grep) 3.4', bash '5.0.17(1)-rele ase (x86_64-pc-linux-gnu)'. Checking TEMP_DIR '/tmp' is a folder and writable (OK) Test - En/Decryption skipped. (GPG disabled) --- Start running command PRE at 21:26:37.615 --- Skipping n/a script '/root/.duply/artifactory_backup/pre'. --- Finished state OK at 21:26:37.628 - Runtime 00:00:00.012 --- --- Start running command BKP at 21:26:37.659 --- Using archive dir: /root/.cache/duplicity/duply_artifactory_backup Using backup name: duply_artifactory_backup GPG binary is gpg, version (2, 2, 19) Import of duplicity.backends.adbackend Succeeded Import of duplicity.backends.azurebackend Succeeded Import of duplicity.backends.b2backend Succeeded Import of duplicity.backends.boxbackend Succeeded Import of duplicity.backends.cfbackend Succeeded Import of duplicity.backends.dpbxbackend Succeeded Import of duplicity.backends.gdocsbackend Succeeded Import of duplicity.backends.gdrivebackend Succeeded Import of duplicity.backends.giobackend Succeeded Import of duplicity.backends.hsibackend Succeeded Import of duplicity.backends.hubicbackend Succeeded Import of duplicity.backends.idrivedbackend Succeeded Import of duplicity.backends.imapbackend Succeeded Import of duplicity.backends.jottacloudbackend Succeeded Import of duplicity.backends.lftpbackend Succeeded Import of duplicity.backends.localbackend Succeeded Import of duplicity.backends.mediafirebackend Succeeded Import of duplicity.backends.megabackend Succeeded Import of duplicity.backends.megav2backend Succeeded Import of duplicity.backends.megav3backend Succeeded Import of duplicity.backends.multibackend Succeeded Import of duplicity.backends.ncftpbackend Succeeded Import of duplicity.backends.onedrivebackend Succeeded Import of duplicity.backends.par2backend Succeeded Import of duplicity.backends.pcabackend Succeeded Import of duplicity.backends.pydrivebackend Succeeded Import of duplicity.backends.rclonebackend Succeeded Import of duplicity.backends.rsyncbackend Succeeded Import of duplicity.backends.s3_boto3_backend Succeeded Multiprocessing is not supported on linux, will use threads instead. Import of duplicity.backends.s3_boto_backend Succeeded Import of duplicity.backends.ssh_paramiko_backend Succeeded Import of duplicity.backends.ssh_pexpect_backend Succeeded Import of duplicity.backends.swiftbackend Succeeded Import of duplicity.backends.sxbackend Succeeded Import of duplicity.backends.tahoebackend Succeeded Import of duplicity.backends.webdavbackend Succeeded Reading globbing filelist /root/.duply/artifactory_backup/exclude Main action: inc Acquiring lockfile b'/root/.cache/duplicity/duply_artifactory_backup/lockfile' duplicity 0.8.19 Args: /usr/bin/duplicity --name duply_artifactory_backup --no-encryption --verbosity 9 --full-if-older-than 7D --volsize 1024 --s3-use-multiprocessing --s3-multipart-chunk-size 512 --allow-source-mismatch --exclude-filelist /root/.duply/artifactory_backup/exclude /labkey boto3+s3://s3-us-west-2.amazonaws.com/BUCKET-NAME/artifactory_backup Linux ip-172-30-115-92 5.4.0-1049-aws #51-Ubuntu SMP Wed May 12 21:13:52 UTC 2021 x86_64 x86_64 /usr/bin/python3 3.8.5 (default, May 27 2021, 13:30:53) [GCC 9.3.0] Using temporary directory /tmp/duplicity-_k91zmc2-tempdir Registering (mkstemp) temporary file /tmp/duplicity-_k91zmc2-tempdir/mkstemp-t1cl2e0h-1 Temp has 138928574464 available, backup will use approx 1395864371. Backtrace of previous error: Traceback (innermost last): File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 384, in inner_retry return fn(self, *args) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 604, in list return
[Bug 1930925] [NEW] Ubuntu 20.04 doesn't work with moidern KVMs
Public bug reported: I have recently acquired a acquired a desktop running ubuntu 20.04. I have several computers and switch between them using this KVM https://www.amazon.co.uk/gp/product/B077SV9MMQ/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8=1 The other machines are either running windows or ubuntu 18.04 or earlier. They are all fine, but the with 20.04 machine neither the keyboard nor the mouse works. On the 18.04 machine I can see lsusb Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub and it is the Logitech, Inc. Unifying Receiver which appears when the USB from the KVM is connected. On the 20.04 machine only this appears lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I have tested installation discs from 19.04 onwards. The failure first appears in 19.10 and is still present in 21.04 I can observe a similar problem with a dual boot laptop running windows 10 and 20.04. With windows 10 I can use it with the KVM for screen and keyboard/mouse, but with ubuntu 20.04 the keyboard and mouse do not work. This issue has also been observed here https://unix.stackexchange.com/questions/646515/using-logitech-mouse- keyboard-on-tesmart-kvm-switch-with-ubuntu-20-04 and I have observed it using a Lindy 2 port HDMI/USB KVM (but I'm unsure of the model). I had to report this originally against xorg as this bug reporting system seems not to allow reporting of bugs against unknown packages. I also had to report it through the ubuntu-bug executable as I've been unable to find a way in launchpad of reporting a bug (as opposed to getting a guided tour about reporting bugs). I am happy to supply more info and test fixes if I am asked but as with this type of bug where something fails to happen rather than something wrong happens I don't know what to look at. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None Date: Fri Jun 4 20:21:15 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2021-05-14 (21 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 11: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 13: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 13: Dev 3, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=0c391c11-c570-4e04-a351-4fd128a75369 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2021 dmi.bios.release: 8.20 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0820 dmi.board.asset.tag: Default string dmi.board.name: PRIME H570M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0820:bd04/27/2021:br8.20:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH570M-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx:
[Bug 1930640] Re: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object
Unfortunately, the same issue is coming up, even after installing the requirements via pip. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/duplicity/backends/_boto_multi.py", line 223, in _upload mp.upload_part_from_file(fd, offset + 1, cb=_upload_callback, File "/usr/lib/python3/dist-packages/boto/s3/multipart.py", line 257, in upload_part_from_file key.set_contents_from_file(fp, headers=headers, replace=replace, File "/usr/lib/python3/dist-packages/boto/s3/key.py", line 1307, in set_contents_from_file self.send_file(fp, headers=headers, cb=cb, num_cb=num_cb, File "/usr/lib/python3/dist-packages/boto/s3/key.py", line 760, in send_file self._send_file_internal(fp, headers=headers, cb=cb, num_cb=num_cb, File "/usr/lib/python3/dist-packages/boto/s3/key.py", line 932, in _send_file_internal self.content_type = mimetypes.guess_type(self.path)[0] File "/usr/lib/python3.8/mimetypes.py", line 292, in guess_type return _db.guess_type(url, strict) File "/usr/lib/python3.8/mimetypes.py", line 117, in guess_type scheme, url = urllib.parse._splittype(url) File "/usr/lib/python3.8/urllib/parse.py", line 1008, in _splittype match = _typeprog.match(url) TypeError: cannot use a string pattern on a bytes-like object There were some errors in the install of packages via pip, but I don't think any of these would have caused this particular issue: ERROR: launchpadlib 1.10.13 requires testresources, which is not installed. ERROR: pyopenssl 20.0.1 has requirement cryptography>=3.2, but you'll have cryptography 2.8 which is incompatible. ERROR: mediafire 0.6.0 has requirement requests<=2.11.1,>=2.4.1, but you'll have requests 2.25.1 which is incompatible. ERROR: debtcollector 2.2.0 has requirement pbr!=2.1.0,>=2.0.0, but you'll have pbr 1.10.0 which is incompatible. ERROR: oslo-i18n 5.0.1 has requirement pbr!=2.1.0,>=2.0.0, but you'll have pbr 1.10.0 which is incompatible. ERROR: stevedore 3.3.0 has requirement pbr!=2.1.0,>=2.0.0, but you'll have pbr 1.10.0 which is incompatible. ERROR: oslo-utils 4.9.0 has requirement pbr!=2.1.0,>=2.0.0, but you'll have pbr 1.10.0 which is incompatible. ERROR: os-service-types 1.7.0 has requirement pbr!=2.1.0,>=2.0.0, but you'll have pbr 1.10.0 which is incompatible. ERROR: keystoneauth1 4.3.1 has requirement pbr!=2.1.0,>=2.0.0, but you'll have pbr 1.10.0 which is incompatible. ERROR: oslo-serialization 4.1.0 has requirement pbr!=2.1.0,>=2.0.0, but you'll have pbr 1.10.0 which is incompatible. ERROR: python-keystoneclient 4.2.0 has requirement pbr!=2.1.0,>=2.0.0, but you'll have pbr 1.10.0 which is incompatible. Shouldn't it also be urllib3 since the above is in python3.5.8? I do have the urllib3 package: pip3 install urllib3 Requirement already satisfied: urllib3 in /usr/lib/python3/dist-packages (1.25.8) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930640 Title: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1930640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908971] Re: TypeError: cannot use a string pattern on a bytes-like object
I ran into the same issue, but upgrading to 0.8.19 didn't fix it. I've put in a new bug for this: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1930640 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908971 Title: TypeError: cannot use a string pattern on a bytes-like object To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1908971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930640] [NEW] Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object
Public bug reported: I followed the solution in https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1908971 (I was running duplicity 0.8.11.1612-1 as well), but after upgrading to 0.8.19, the problem still persists for me when trying to use S3 multipart uploads. Note: This problem doesn't appear to exist in duplicity 0.7.17 running on python2.7, which is making me wonder if this is a python3.8 related issue. user@host:~$ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 user@host:~$ apt-cache policy duplicity duplicity: Installed: 0.8.19-ppa202104291804~ubuntu20.04.1 Candidate: 0.8.19-ppa202104291804~ubuntu20.04.1 Version table: *** 0.8.19-ppa202104291804~ubuntu20.04.1 500 500 http://ppa.launchpad.net/duplicity-team/duplicity-release-git/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 0.8.11.1612-1 500 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu focal/main amd64 Packages Start duply v2.2, time is 2021-06-02 22:58:11. Using profile '/root/.duply/artifactory_backup'. Using installed duplicity version 0.8.19, python 3.8.5 (/usr/bin/python3), gpg 2.2.19 (Home: /root/.gnupg), awk 'GNU Awk 5.0.1, API: 2.0 (GNU MPFR 4.0.2, GNU MP 6.2.0)', grep 'grep (GNU grep) 3.4', bash '5.0.17(1)-release (x86_64-pc-linux-gnu)'. Checking TEMP_DIR '/tmp' is a folder and writable (OK) Test - En/Decryption skipped. (GPG disabled) --- Start running command PRE at 22:58:11.550 --- Skipping n/a script '/root/.duply/artifactory_backup/pre'. --- Finished state OK at 22:58:11.563 - Runtime 00:00:00.013 --- --- Start running command BKP at 22:58:11.595 --- Using archive dir: /root/.cache/duplicity/duply_artifactory_backup Using backup name: duply_artifactory_backup GPG binary is gpg, version (2, 2, 19) Import of duplicity.backends.adbackend Succeeded Import of duplicity.backends.azurebackend Succeeded Import of duplicity.backends.b2backend Succeeded Import of duplicity.backends.boxbackend Failed: No module named 'boxsdk' Import of duplicity.backends.cfbackend Succeeded Import of duplicity.backends.dpbxbackend Succeeded Import of duplicity.backends.gdocsbackend Succeeded Import of duplicity.backends.gdrivebackend Succeeded Import of duplicity.backends.giobackend Succeeded Import of duplicity.backends.hsibackend Succeeded Import of duplicity.backends.hubicbackend Succeeded Import of duplicity.backends.idrivedbackend Succeeded Import of duplicity.backends.imapbackend Succeeded Import of duplicity.backends.jottacloudbackend Succeeded Import of duplicity.backends.lftpbackend Succeeded Import of duplicity.backends.localbackend Succeeded Import of duplicity.backends.mediafirebackend Succeeded Import of duplicity.backends.megabackend Succeeded Import of duplicity.backends.megav2backend Succeeded Import of duplicity.backends.megav3backend Succeeded Import of duplicity.backends.multibackend Succeeded Import of duplicity.backends.ncftpbackend Succeeded Import of duplicity.backends.onedrivebackend Succeeded Import of duplicity.backends.par2backend Succeeded Import of duplicity.backends.pcabackend Succeeded Import of duplicity.backends.pydrivebackend Succeeded Import of duplicity.backends.rclonebackend Succeeded Import of duplicity.backends.rsyncbackend Succeeded Import of duplicity.backends.s3_boto3_backend Succeeded Multiprocessing is not supported on linux, will use threads instead. Import of duplicity.backends.s3_boto_backend Succeeded Import of duplicity.backends.ssh_paramiko_backend Succeeded Import of duplicity.backends.ssh_pexpect_backend Succeeded Import of duplicity.backends.swiftbackend Succeeded Import of duplicity.backends.sxbackend Succeeded Import of duplicity.backends.tahoebackend Succeeded Import of duplicity.backends.webdavbackend Succeeded Setting multipart boto backend process pool to 4 processes Reading globbing filelist /root/.duply/artifactory_backup/exclude Main action: inc Acquiring lockfile b'/root/.cache/duplicity/duply_artifactory_backup/lockfile' duplicity 0.8.19 Args: /usr/bin/duplicity --name duply_artifactory_backup --no-encryption --verbosity 9 --full-if-older-than 7D --volsize 1024 --s3-use-multiprocessing --s3-multipart-chunk-size 512 --allow-source-mismatch --exclude-filelist /root/.duply/artifactory_backup/exclude /MyDirectory s3://s3-us-west-2.amazonaws.com/BUCKET-NAME/artifactory_backup Linux ip-172-30-115-92 5.4.0-1047-aws #49-Ubuntu SMP Wed Apr 28 22:47:04 UTC 2021 x86_64 x86_64 /usr/bin/python3 3.8.5 (default, May 27 2021, 13:30:53) [GCC 9.3.0] === Log errors: Attempt 4 failed. BackendException: Multipart upload failed. Aborted. Writing duplicity-full.20210602T225820Z.vol1.difftar.gz Uploading s3://s3-us-west-2.amazonaws.com/BUCKET-NAME/artifactory_backup/duplicity-full.20210602T225820Z.vol1.difftar.gz to STANDARD Storage Uploading 1073705932 bytes in 2 chunks Waiting for the pool to finish processing 2 tasks
[Bug 1929293] [NEW] qmil-run sets up the wrong symbolic links so qmail won't start
Public bug reported: >From a fresh installation of qmail I find jon@frobenius:/etc/qmail/qmail-send$ ls -l supervise lrwxrwxrwx 1 root root 29 May 21 20:17 supervise -> /var/lib/supervise/qmail-send jon@frobenius:/etc/qmail/qmail-send$ ls -l /var/lib/qmail/supervise/ total 12 lrwxrwxrwx 1 root root 21 Mar 3 2015 qmail-send -> /etc/qmail/qmail-send drwx-- 2 root root 4096 May 22 12:23 qmail-send.log lrwxrwxrwx 1 root root 22 Mar 3 2015 qmail-smtpd -> /etc/qmail/qmail-smtpd drwx-- 2 root root 4096 May 22 12:23 qmail-smtpd.log lrwxrwxrwx 1 root root 23 Mar 3 2015 qmail-verify -> /etc/qmail/qmail-verify drwx-- 2 root root 4096 May 22 12:23 qmail-verify.log jon@frobenius:/var/lib$ sudo qmailctl start Starting qmail qmail-send supervise not running qmail-smtpd supervise not running qmail-verify supervise not running jon@frobenius:/var/lib$ sudo qmailctl stat /etc/service/qmail-send: unable to open supervise/ok: file does not exist /etc/service/qmail-send/log: unable to open supervise/ok: file does not exist /etc/service/qmail-smtpd: unable to open supervise/ok: file does not exist /etc/service/qmail-smtpd/log: unable to open supervise/ok: file does not exist /etc/service/qmail-verify: unable to open supervise/ok: file does not exist /etc/service/qmail-verify/log: unable to open supervise/ok: file does not exist messages in queue: 0 messages in queue but not yet preprocessed: 0 The problem occurs because the files supervise all point to a non- existent directory /var/lib/supervise. The correct directory is /var/lib/qmail/supervise This can be overcome with jon@frobenius:/var/lib$ sudo ln -s qmail/supervise supervise jon@frobenius:/var/lib$ sudo qmailctl start Starting qmail jon@frobenius:/var/lib$ sudo qmailctl stat /etc/service/qmail-send: up (pid 57710) 3 seconds /etc/service/qmail-send/log: up (pid 57722) 3 seconds /etc/service/qmail-smtpd: up (pid 57713) 3 seconds /etc/service/qmail-smtpd/log: up (pid 57721) 3 seconds /etc/service/qmail-verify: up (pid 57720) 3 seconds /etc/service/qmail-verify/log: up (pid 57723) 3 seconds messages in queue: 0 messages in queue but not yet preprocessed: 0 But, I believe the correct fix is to create the correct links from the subdirectories of /etc/qmail jon@frobenius:/var/lib$ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release: 20.04 jon@frobenius:/var/lib$ apt-cache policy qmail-run qmail-run: Installed: 2.0.2+nmu1 Candidate: 2.0.2+nmu1 Version table: *** 2.0.2+nmu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu focal/universe i386 Packages 100 /var/lib/dpkg/status I expected qmail to start, and qmailctl stat to show me it running. Instead I got the error messages above ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: qmail qmail-run ** Attachment added: "/var/log/syslog" https://bugs.launchpad.net/bugs/1929293/+attachment/5499443/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929293 Title: qmil-run sets up the wrong symbolic links so qmail won't start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1929293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929292] [NEW] ubiquity crashes whilst trying to use ubuntu-bug
Public bug reported: Multiple identities can be used for authentication: 1. user,,, (user) 2. Jon Thackray,,, (jon) Choose identity to authenticate as (1-2): 2 Password: polkit-agent-helper-1: pam_authenticate failed: Authentication failure AUTHENTICATION FAILED === Error executing command as another user: Not authorized This incident has been reported. ERROR: hook /usr/share/apport/package-hooks/source_ubiquity.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/package-hooks/source_ubiquity.py", line 158, in add_info add_installation_log(report, 'Casper', 'casper.log') File "/usr/share/apport/package-hooks/source_ubiquity.py", line 29, in add_installation_log if isinstance(report[ident], bytes): File "/usr/lib/python3.8/collections/__init__.py", line 1010, in __getitem__ raise KeyError(key) KeyError: 'Casper' My installation doesn't have /var/log/partman jon@frobenius:/var/lib$ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 jon@frobenius:/var/lib$ apt-cache policy ubiquity ubiquity: Installed: (none) Candidate: 20.04.15.11 Version table: 20.04.15.11 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 20.04.15 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages I expected to be able to report a bug I've found in qmail-run, but this seems to be a barrier to entry Instead I got to report ubiquity preventing me from reporting a bug ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat May 22 13:36:26 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2021-05-14 (8 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.10 ** Attachment added: "/var/log/syslog" https://bugs.launchpad.net/bugs/1929292/+attachment/5499437/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929292 Title: ubiquity crashes whilst trying to use ubuntu-bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1929292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922135] [NEW] package grub-efi-amd64-signed 1.142.11+2.04-1ubuntu26.9 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit s
Public bug reported: crashed on upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: grub-efi-amd64-signed 1.142.11+2.04-1ubuntu26.9 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Mar 31 10:43:01 2021 ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 255 InstallationDate: Installed on 2019-12-09 (477 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.142.11+2.04-1ubuntu26.9 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 255 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2-signed (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/1922135 Title: package grub-efi-amd64-signed 1.142.11+2.04-1ubuntu26.9 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 255 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1922135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915984] [NEW] Disk Usage Analyzer no longer functions at all; freezes several seconds after start
Public bug reported: Disk Usage Analyzer no longer works at all; becomes unresponsive several seconds after starting ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: baobab 3.34.0-1 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 17 21:50:12 2021 InstallationDate: Installed on 2020-09-29 (141 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: baobab UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: baobab (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/1915984 Title: Disk Usage Analyzer no longer functions at all; freezes several seconds after start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/baobab/+bug/1915984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913613] Re: Second monitor is detected but has no signal
** Description changed: xrandr Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384 eDP connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm -1920x1080 59.93*+ 39.99 -1680x1050 59.93 -1280x1024 59.93 -1440x900 59.93 -1280x800 59.93 -1280x720 59.93 -1024x768 59.93 -800x600 59.93 -640x480 59.93 + 1920x1080 59.93*+ 39.99 + 1680x1050 59.93 + 1280x1024 59.93 + 1440x900 59.93 + 1280x800 59.93 + 1280x720 59.93 + 1024x768 59.93 + 800x600 59.93 + 640x480 59.93 HDMI-1-0 connected (normal left inverted right x axis y axis) -1920x1080 60.00 + 59.9450.00 -1680x1050 59.95 -1600x900 60.00 -1280x1024 75.0260.02 -1280x800 59.81 -1280x720 60.0059.9450.00 -1024x768 75.0360.00 -800x600 75.0060.32 -720x576 50.00 -720x480 59.94 -640x480 75.0059.9459.93 + 1920x1080 60.00 + 59.9450.00 + 1680x1050 59.95 + 1600x900 60.00 + 1280x1024 75.0260.02 + 1280x800 59.81 + 1280x720 60.0059.9450.00 + 1024x768 75.0360.00 + 800x600 75.0060.32 + 720x576 50.00 + 720x480 59.94 + 640x480 75.0059.9459.93 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/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 460.32.03 Sun Dec 27 19:00:34 UTC 2020 - GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.32.03 Sun Dec 27 19:00:34 UTC 2020 + GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 BootLog: - + CompositorRunning: None Date: Thu Jan 28 16:52:43 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: - nvidia, 460.32.03, 5.4.0-64-generic, x86_64: installed - rtl8821ce, 5.5.2.1, 5.4.0-42-generic, x86_64: installed - rtl8821ce, 5.5.2.1, 5.4.0-64-generic, x86_64: installed + nvidia, 460.32.03, 5.4.0-64-generic, x86_64: installed + rtl8821ce, 5.5.2.1, 5.4.0-42-generic, x86_64: installed + rtl8821ce, 5.5.2.1, 5.4.0-64-generic, x86_64: installed GraphicsCard: - NVIDIA Corporation Device [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. Device [1043:109f] - Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. Device [1043:18f1] + NVIDIA Corporation Device [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. Device [1043:109f] + Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. Device [1043:18f1] InstallationDate: Installed on 2021-01-27 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT ProcEnviron: - LANGUAGE=es - TERM=xterm-256color - PATH=(custom, no user) - LANG=es_ES.UTF-8 - SHELL=/bin/bash + LANGUAGE=es + TERM=xterm-256color + PATH=(custom, no user) + LANG=es_ES.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=a4e7f6c4-6b4b-46b3-b120-84a8805ac9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX505DT.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX505DT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias:
[Bug 1913613] [NEW] Second monitor is detected but has no signal
Public bug reported: xrandr Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384 eDP connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm 1920x1080 59.93*+ 39.99 1680x1050 59.93 1280x1024 59.93 1440x900 59.93 1280x800 59.93 1280x720 59.93 1024x768 59.93 800x600 59.93 640x480 59.93 HDMI-1-0 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 59.9450.00 1680x1050 59.95 1600x900 60.00 1280x1024 75.0260.02 1280x800 59.81 1280x720 60.0059.9450.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/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 460.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 BootLog: CompositorRunning: None Date: Thu Jan 28 16:52:43 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 460.32.03, 5.4.0-64-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-42-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-64-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:109f] Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:18f1] InstallationDate: Installed on 2021-01-27 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT ProcEnviron: LANGUAGE=es TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=a4e7f6c4-6b4b-46b3-b120-84a8805ac9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX505DT.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX505DT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX505DT.315:bd09/22/2020:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505DT_FX505DT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505DT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming dmi.product.name: TUF Gaming FX505DT_FX505DT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic corruption ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913613 Title: Second monitor is detected but has no signal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1913613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805666] Re: Evolution Alarm Notify continues pop-up reminders even though notifications disabled
Same issue for me as I'd like general notifications just not routed to Gnome via the Evolution popup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805666 Title: Evolution Alarm Notify continues pop-up reminders even though notifications disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1805666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909815] [NEW] "Could not install 'oracle-java11-installer-local' always happens when attempting upgrades
Public bug reported: Using Ubuntu 18.04. Got prompted to upgrade to 20.04 again today. Tried before but never works. Today I got the following info on screen. Could not install 'oracle-java11-installer-local' The upgrade will continue but the 'oracle-java11-installer-local' package may not be in a working state. Please consider submitting a bug report about it. Installed oracle-java11-installer-local package post installation script subprocess returned error exit state 1 Could not install the upgrades The upgrade has aborted. A recovery will now run (dpkg - configure -a). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.41 ProcVersionSignature: Ubuntu 4.15.0-128.131-generic 4.15.18 Uname: Linux 4.15.0-128-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Jan 1 15:18:11 2021 InstallationDate: Installed on 2018-08-10 (875 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to bionic on 2021-01-01 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909815 Title: "Could not install 'oracle-java11-installer-local' always happens when attempting upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1909815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
I can deterministically reproduce this crash with Wireguard on the RPI3 running 20.10 and hence using the lan78xx driver on eth0. A few minutes of browsing public web sites on a client connected through Wireguard to the RPI3 crashes the RPI. Changing nothing except for running Wireguard's forwarding through wlan0 rather than eth0 does not result in any crashes. So certainly seems to indicate that the wired ethernet's lan78xx driver shipping today with 20.10 is the culprit causing these crashes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996916] Re: postgresql packages in the removal blacklist making it hard to upgrade
@Quinn - Same problem, since you say its a different bug I went ahead and opened one with the dist-upgrade log: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1907652 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996916 Title: postgresql packages in the removal blacklist making it hard to upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/996916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907652] [NEW] postgresql packages in the removal blacklist making it hard to upgrade
Public bug reported: PostGIS and PGRouting are in the removal blacklist, making it hard to upgrade from 18.04 LTS to 20.04 LTS dist-upgrade main.log: 2020-12-10 11:51:35,686 DEBUG blacklist expr '^postgresql-.*[0-9]\.[0-9].*' matches 'postgresql-10-postgis-2.4' 2020-12-10 11:51:35,686 DEBUG The package 'postgresql-10-postgis-2.4' is marked for removal but it's in the removal blacklist 2020-12-10 11:51:50,878 ERROR Dist-upgrade failed: 'The package 'postgresql-10-postgis-2.4' is marked for removal but it is in the removal blacklist.' 2020-12-10 11:51:50,885 DEBUG abort called 2020-12-10 11:51:50,887 DEBUG openCache() 2020-12-10 11:51:53,377 DEBUG Comparing 4.15.0-126 with 2020-12-10 11:51:53,381 DEBUG Comparing 5.3.0-61 with 4.15.0-126 2020-12-10 11:51:53,382 DEBUG Comparing 5.4.0-54 with 5.3.0-61 2020-12-10 11:51:53,382 DEBUG Comparing 5.4.0-56 with 5.4.0-54 2020-12-10 11:51:53,596 DEBUG /openCache(), new cache size 100643 ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: dist-upgrade ** Tags added: dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907652 Title: postgresql packages in the removal blacklist making it hard to upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1907652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904230] Re: System freeze after logging onto desktop session
'journalctl -b -1' comes back with: Specifying boot ID has no effect, no persistent journal was found I'm assuming though you're after the boot log for the previous session (that froze) so I've manually extracted this from /var/log/syslog in the attached archive (prevboot.txt). Unfortunately nothing new was added to /var/crash as a result of the freeze. Something additional to mention which may be related (given it's display related), I had to reboot the machine a couple of times to get this as it seemingly had issues starting the display manager. Visually the display kept flicking between the boot log and another one with some further logging info. The graphical login screen was never displayed. Syslog was showing messages as follows: Nov 18 19:58:57 monolith systemd[1]: Starting LXDE Display Manager... Nov 18 19:58:57 monolith systemd[1]: Started LXDE Display Manager. Nov 18 19:59:02 monolith systemd[1]: lxdm.service: Main process exited, code=exited, status=1/FAILURE Nov 18 19:59:02 monolith systemd[1]: lxdm.service: Unit entered failed state. Nov 18 19:59:02 monolith systemd[1]: lxdm.service: Failed with result 'exit-code'. Nov 18 19:59:03 monolith systemd[1]: lxdm.service: Service hold-off time over, scheduling restart. Nov 18 19:59:03 monolith systemd[1]: Stopped LXDE Display Manager. Only fix was to reboot it. I've attached the boot log for this one as 'prevboot1.txt'. This problem happened on two different boots. ** Attachment added: "boot logs" https://bugs.launchpad.net/ubuntu/+bug/1904230/+attachment/5435802/+files/logs.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904230 Title: System freeze after logging onto desktop session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1904230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
same fail. literally last10 seconds fail error message. dual boot installation on two nvme drives Acer Nitro5 AN5-15-55 pls help ,, is there a workaround? I been using Ubuntu last 8 yrs cant live without it. I triede 20.04 and 20.10 with install thrid party drivers elected and install updates not selected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1871268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904230] Re: System freeze after logging onto desktop session
I have managed to upload the crash report via another machine, the ID is 1904626. For some reason it appears to be associated with bash which makes me wonder if it is related - the timestamp is roughly 6 minutes after restarting the machine from the freeze which puts it in the right time frame but could be coincidental. I will endeavor to repeat the crash and see if a new one is reported. I've noted your comments regarding support and understand. The fact it crops up with two different desktops though - LXDM and Openbox could suggest though it's possibly part of 'X' rather than one of these. Unfortunately as you know, it's not possible to move from 2016 to 2020.04 in one move without going via 2018 first, I plan to do that over the next few months but there is a fair amount of work involved in ensuring everything is working after an upgrade so it's not something I have time for right now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904230 Title: System freeze after logging onto desktop session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1904230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904230] Re: System freeze after logging onto desktop session
There is one crash report in the /var/crash folder which corresponds to the last time the system restarted due to this issue (other instances are >7 days so will have been removed). Running ubuntu-bug as requested generated a lot of dots but did not provide a bug ID: jon@monolith:/var/crash$ ubuntu-bug _bin_bash.500.crash *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (583.0 KB) E: Examine locally V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/E/V/K/I/C): S *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. [..] ..... jon@monolith:/var/crash$ There does not appear to be anything captured recently on https://errors.ubuntu.com/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904230 Title: System freeze after logging onto desktop session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1904230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904230] [NEW] System freeze after logging onto desktop session
Public bug reported: After performing a recent update, I am encountering a complete system freeze shortly after logging on to a graphical session but only for a single user (which may suggest a corrupted configuration file somewhere). This is repeatable - happens every time I attempt to login. The desktop is LXDE however it also occurs with Openbox as well. Furthermore, it also happens when launching a desktop with vncserver which suggests it is not a graphics driver issue. I've tried deleting (renaming) the .config and .cache folders in the account, neither of these have had any effect. Am fairly sure I have seen this once or twice in the past but it was a pretty rare event. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-122.124~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.25 Architecture: amd64 Date: Fri Nov 13 17:44:30 2020 InstallationDate: Installed on 2013-07-25 (2668 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to xenial on 2018-12-28 (686 days ago) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904230 Title: System freeze after logging onto desktop session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1904230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714244] Re: [snap] apparmor denials on /etc/chromium-browser/policies/
Running Chromium Version 86.0.4240.111 (Official Build) snap (64-bit) on Ubuntu 20.04 and I'm not seeing my policies enforced inside Chromium. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714244 Title: [snap] apparmor denials on /etc/chromium-browser/policies/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1714244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769890] Re: Icingaweb2 does not work with PHP 7.2
I installed a Bionic VM with the minimal .iso. Followed my steps to reproduce this fault and got the error in my browser. I then properly read Brian's instructions on how to use "proposed" and now get the Icinga web 2 setup wizard in my browser. I'll keep the VM around for a few weeks if you need anything more testing. Thanks for fixing the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769890 Title: Icingaweb2 does not work with PHP 7.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icingaweb2/+bug/1769890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected
I have encountered this issue trying a fresh install of Kubuntu 20.04.1. The entire reason that I tried a fresh install is that trying to upgrade my existing system from Ubuntu Mate 18.04 to 20.04 resulted in the upgrade finishing with errors and leaving my system in an unusable state (fortunately, I have a full backup, so rolling back a failed upgrade is painless, other than the time consumed). I don't know if the root cause of both issues is the same or not. My graphics card is an NVidia GeForce GTX 750 Ti. /var/log/syslog from the failed ground-up installation is attached (I attempted installing twice in the live session with failures both times). I will attempt to find time to retry the upgrade and attach the syslog from that so we can see if the root cause is the same (I have already rolled the filesystem back from backup for the previous attempts, so I don't have a syslog for them). The end result is that I have no upgrade path from 18.04 to 20.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails when "Install Third-Party Drivers" is selected To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1871268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected
** Attachment added: "The attachment for my comment above does not seem to have taken. This is /var/log/syslog for a failed ground-up Kubuntu 20.04 installation" https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1871268/+attachment/5417422/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails when "Install Third-Party Drivers" is selected To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1871268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897339] [NEW] Documentation missing for "ip tuntap"
Public bug reported: Ubuntu 18.04.5 iproute2 4.15.0-2ubuntu1.2 iproute2-doc 4.15.0-2ubuntu1.2 Most of the subcommands for /sbin/ip are documented in a manpage with a name of the form "ip-$SUBCOMMAND(8)", for example "ip address" is documented at "ip-address(8)". However, ip tuntap seems to be completely undocumented, other than the one-line description given in ip(8): "tuntap - manage TUN/TAP devices." No manpage is pulled in with the iproute2 package, as with the other ip manpages, nor with the iproute2-doc package. This also seems to be the case with "ip mrule". Expected behavior: Some package can be installed that contains a manpage covering "ip tuntap". Actual behavior: No manpage for "ip tuntap" exists in either the package that contains the /sbin/ip binary, nor the corresponding -doc package. ** Affects: iproute2 (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/1897339 Title: Documentation missing for "ip tuntap" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1897339/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
RE: [Bug 1889223] Re: vc4-kms-v3d boot failure focal armhf preinstalled server
How is it not a bug when the kernel fails to boot when you use the default setting? There is a workaround for this problem which is to limit memory, but there is still a crash. The Raspbian kernel doesn't crash -- it works. That would suggest there is a problem here. JW -Original Message- From: boun...@canonical.com On Behalf Of Kyle Nitzsche Sent: Friday, September 25, 2020 2:54 PM To: Jonathan Watson Subject: [Bug 1889223] Re: vc4-kms-v3d boot failure focal armhf preinstalled server - - - external message, proceed with caution - - - OK, so you are saying it is really not a kernel fix but is rather an enablement file change/config. thanks. -- You received this bug notification because you are subscribed to the bug report. https://urldefense.com/v3/__https://bugs.launchpad.net/bugs/1889223__;!!LrkQbg!egKH44YGlhhBxV6R0RjD7KoXnEZBg3YTxHTuKvnvxop_BsoVCnxlp3XXKcFapU0pLA8$ Title: vc4-kms-v3d boot failure focal armhf preinstalled server Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi source package in Focal: Triaged Bug description: Booting 20.04 armhf preinstalled-server on Pi3b+ with vc4-kms-v3d selected [1] causes boot failure with [2] output on UART. Further system info in [3] Side note: Booting with the same usercfg.txt but with the 18.04 vc4 -kms-v3d.dtbo file "works": the boot is normal without the errors shown in [2]. [1] ubuntu@ubuntu:~$ cat /boot/firmware/usercfg.txt # Place "config.txt" changes (dtparam, dtoverlay, disable_overscan, etc.) in # this file. Please refer to the README file for a description of the various # configuration files on the boot partition. dtoverlay=vc4-kms-v3d [2] Starting kernel ... [0.039873] cma: CMA area linux,cma could not be activated [0.043189] DMA: failed to allocate 1024 KiB pool for atomic coherent allocation [0.308022] kobject_add_internal failed for 3e513000.framebuffer with -EEXIST, don't try to register things with the s. [1.141370] kvm [1]: Error, CPU 0 not supported! [1.235565] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 0 config (-12 80) [1.236723] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 1 config (-12 81) [1.237882] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 2 config (-12 82) [1.239014] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 3 config (-12 83) [1.240139] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 4 config (-12 84) [1.241263] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 5 config (-12 85) [1.242412] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 6 config (-12 86) [1.243526] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 7 config (-12 87) [1.831440] spi-bcm2835 3f204000.spi: could not get clk: -517 [1.849256] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 2 config (-12 82) [1.850523] raspberrypi-exp-gpio soc:firmware:expgpio: Failed to get GPIO 2 config (-12 82) [1.852205] bcm2835_vchiq 3f00b840.mailbox: could not allocate DMA memory [2.369653] spi-bcm2835 3f204000.spi: cannot prepare fill_tx_desc - not using DMA mode [2.412710] sdhost: failed to allocate log buf ext4 [3] ubuntu@ubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal ubuntu@ubuntu:~$ uname -a Linux ubuntu 5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:37:25 UTC 2020 armv7l armv7l armv7l GNU/Linux Initial part of lshw: ubuntu description: ARMv7 Processor rev 4 (v7l) product: Raspberry Pi 3 Model B Plus Rev 1.3 serial: 92021ecd width: 32 bits capabilities: smp To manage notifications about this bug go to: https://urldefense.com/v3/__https://bugs.launchpad.net/ubuntu/*source/linux-raspi/*bug/1889223/*subscriptions__;Kysr!!LrkQbg!egKH44YGlhhBxV6R0RjD7KoXnEZBg3YTxHTuKvnvxop_BsoVCnxlp3XXKcFaa3gqjsM$ --- CONFIDENTIALITY NOTICE: This message is for intended addressee(s) only and may contain information that is confidential, proprietary or exempt from disclosure. If you are not the intended recipient, please contact the sender immediately. Unauthorized use or distribution is prohibited and may be unlawful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889223 Title: vc4-kms-v3d boot failure focal armhf preinstalled server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1889223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
Still doesn't work for me after all updates，and there are side effects... Now every time I boot up, the Desktop's font is very small, even there is no external monitor...if ALT + F2 -> R, then restore :( libmutter-6-0: Installed: 3.36.4-0ubuntu0.20.04.2 Candidate: 3.36.4-0ubuntu0.20.04.2 Version table: *** 3.36.4-0ubuntu0.20.04.2 500 500 http://cn.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-3ubuntu3 500 500 http://cn.archive.ubuntu.com/ubuntu focal/main amd64 Packages +-+ | NVIDIA-SMI 440.64 Driver Version: 440.64 CUDA Version: 10.2 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===+==+==| | 0 GeForce MX150 Off | :03:00.0 Off | N/A | | N/A 55CP0N/A / N/A |630MiB / 2002MiB | 7% Default | +---+--+--+ journalctl.log => restart,Desktop's font NG journalctl_r.log=> Alt+F2->r ,Desktop's font OK ** Attachment added: "journalctl.zip" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+attachment/5405332/+files/journalctl.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322441] Re: QEMU Windows guest unstable after random amount of time
Changing the status of this bug from 'expired' to 'confirmed', since all the way up here in Ubuntu 20 land (in 2020), I have found this bug when development testing my research OS. Random lockups and segfaults, after which the CPU usage of the qemu-system-x86 process sticks at over 100%. ** Changed in: linux (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322441 Title: QEMU Windows guest unstable after random amount of time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889926] Re: Can't access gpio mapped memory on focal armhf server on pi
We completed a test this morning with the modified pigpio library and verified our applications can now read the GPIO signals once we removed the PROT_EXEC flags from the library init code. We will pursue getting a change in with the pigpio library separately. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889926 Title: Can't access gpio mapped memory on focal armhf server on pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1889926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889926] Re: Can't access gpio mapped memory on focal armhf server on pi
We are going to try editing the pigpio library and rebuilding it and seeing if it works. There doesn't appear to be a clear requirement for pigpio to rely on PROT_EXEC and it has been removed in the past. Conversation about this is happening here: https://github.com/joan2937/pigpio/issues/375 ** Bug watch added: github.com/joan2937/pigpio/issues #375 https://github.com/joan2937/pigpio/issues/375 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889926 Title: Can't access gpio mapped memory on focal armhf server on pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1889926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889223] Re: vc4-kms-v3d boot failure focal armhf preinstalled server
Qt responded and thinks cma-128 will work for our application. I modified our Pi test unit to use the original Ubuntu 20.04 .dtbo file and booted successfully when I used the dtoverlay=vc4-kms-v3d,cma-64 setting. I will test our UI with this configuration early next week. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889223 Title: vc4-kms-v3d boot failure focal armhf preinstalled server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1889223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
Will those changes be merged into the 20.04.1 release? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
