[Bug 2060727] Re: The keyboard does not work after latest kernel update
Have this problem on a Dell XPS 13 running Ubuntu 23.10, kernel 6.5.0-35-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060727 Title: The keyboard does not work after latest kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all
Support should be added to the kernel as of:
b257187bcff4 ("ALSA: hda: cs35l41: Support additional ASUS Zenbook 2022
Models")
And firmware as of:
771968c68191 ("linux-firmware: Add firmware for Cirrus CS35L41 on ASUS
Laptops")
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1981433
Title:
[Asus Zenbook UX3402ZA] Sound doesn't work at all
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux-firmware/+bug/1981433/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1273764] Re: Grub ignores TIMEOUT options on /etc/default/grub
This persists and should be simple to replicate. Why has it has no attention? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1273764 Title: Grub ignores TIMEOUT options on /etc/default/grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1273764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809174] Re: apt doesn't detect file corruption in /var/lib/apt/lists
Just saw this on some field units that are iOT type devices and sometimes get shutdown non-cleanly. We run apt-update on startup and we noticed one machine would not update and had no knowledge of any packages in one of the repos in the sources.list. We noticed the Packages file has 0 size, and no amount of apt update or apt-cache clean could fix it besides deleting/removing the corrupt file. Deleting it resolved the issue: ``` $ ls -lat /var/lib/apt/lists/ total 71252 drwx-- 2 _apt root 4096 Apr 23 16:18 partial drwxr-xr-x 5 root root 4096 Apr 23 15:40 .. drwxr-xr-x 4 root root 4096 Apr 22 21:13 . -rw-r--r-- 1 root root 4342 Apr 22 20:12 [redacted-package-server]-experimental_dists_focal_InRelease -rw-r--r-- 1 root root0 Apr 22 20:12 [redacted-package-server]-experimental_dists_focal_main_binary-amd64_Packages -rw-r--r-- 1 root root 4362 Jan 27 2023 [redacted-package-server]-ubuntu-experimental_dists_focal_InRelease ``` Note the 0 file size on the `[redacted-package- server]-experimental_dists_focal_main_binary-amd64_Packages` file. During this time, it would not Get any new information from the package server. Even with updates pushed to the package server. After removing the file, it does a `Get` and now can see all the packages again: $ sudo mv /var/lib/apt/lists/[redacted-package-server]-experimental_dists_focal_main_binary-amd64_Packages $ sudo apt update Hit:1 [redacted-server]-experimental focal InRelease Hit:2 [redacted-server]-ubuntu-experimental focal InRelease Get:3 [redacted-server]-experimental focal/main amd64 Packages [3524 kB] Fetched 3524 kB in 6s (571 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 27 packages can be upgraded. Run 'apt list --upgradable' to see them. ``` Server software is aptly. apt version is `apt 2.0.6 (amd64)` Happy to track this down and submit a patch for checking the file size of 0, or the algorithm as suggested above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809174 Title: apt doesn't detect file corruption in /var/lib/apt/lists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1809174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061744] [NEW] Evolution crashes on launch with a missing library: /usr/lib/evolution-data-server/camel-providers/libcamelrss.so
Public bug reported: ubuntu@ubuntu:~$ evolution (process:23406): e-data-server-WARNING **: 08:04:00.506: module_load: libevolution-rss-common.so: cannot open shared object file: No such file or directory Failed to load module: /usr/lib/evolution/modules/module-rss.so (evolution:23406): camel-CRITICAL **: 08:04:00.597: camel_provider_list: Could not load /usr/lib/evolution-data-server/camel- providers/libcamelrss.so: libevolution-rss-common.so: cannot open shared object file: No such file or directory (evolution-alarm-notify:23421): camel-CRITICAL **: 08:04:00.962: camel_provider_list: Could not load /usr/lib/evolution-data-server/camel-providers/libcamelrss.so: libevolution-rss-common.so: cannot open shared object file: No such file or directory bwrap: Creating new namespace failed: Permission denied ** (evolution:23406): ERROR **: 08:04:01.075: Failed to fully launch dbus-proxy: Child process exited with code 1 Trace/breakpoint trap (core dumped) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: evolution 3.52.0-1build2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.496 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Tue Apr 16 08:09:58 2024 LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ** Attachment added: "Screenshot from 2024-04-15 21-51-55.png" https://bugs.launchpad.net/bugs/2061744/+attachment/5766054/+files/Screenshot%20from%202024-04-15%2021-51-55.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061744 Title: Evolution crashes on launch with a missing library: /usr/lib/evolution-data-server/camel-providers/libcamelrss.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/2061744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2044657] Re: Multiple data corruption issues in zfs
Actually, it may not be an issue even for Jammy HWE. My copy shows block cloning as an option that's off. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: Multiple data corruption issues in zfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2044657] Re: Multiple data corruption issues in zfs
This issue is different. It's another problem with block copy. But that's known to still be an issue. It's why block copy is disabled in 2.2.1. This is only an issue for the Jammy HWE, which has 2.2.0. No one should be shipping 2.2.0 with anything. It should be replaced with 2.2.1 at least. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: Multiple data corruption issues in zfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058050] Re: gcc-13 build-depends on gcc-multilib if !cross, not if cross
Same result with export DEB_BUILD_PROFILES="nobiarch nocross" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058050 Title: gcc-13 build-depends on gcc-multilib if !cross, not if cross To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-13/+bug/2058050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058050] [NEW] gcc-13 build-depends on gcc-multilib if !cross, not if cross
Public bug reported: export DEB_BUILD_PROFILES=nocross apt build-dep gcc-13 installs gcc-multilib, gnat-13, gdc-13, and 21 more lib32... & etc. These should be installed for cross, not norcross Version noble 13.2.0-4ubuntu3 ** Affects: gcc-13 (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/2058050 Title: gcc-13 build-depends on gcc-multilib if !cross, not if cross To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-13/+bug/2058050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056335] [NEW] /etc/nfsmount.conf doesn't work for servers
Public bug reported: 24.04 nightly from March 5. This is a regression from 20.04. The same problem is present in 22.04 /etc/nfsmount.conf allows specifications of per-server options. with the following: [ NFSMount_Global_Options ] vers=3 rsize=65536 wsize=393216 [ Server "communis.lcsr.rutgers.edu" ] vers=4.2 [ Server "eternal.lcsr.rutgers.edu" ] vers=4.2 communis.lcsr.rutgers.edu uses version 3. eternal.lcsr.rutgers.edu uses 4.2. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nfs-common 1:2.6.3-3ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 .etc.nfs.conf.d.contexttime.conf: [gssd] context-timeout=600 .etc.request-key.d.id_resolver.conf: create id_resolver * * /usr/sbin/nfsidmap -t 600 %k %d ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Mar 6 10:11:48 2024 InstallationDate: Installed on 2024-03-05 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240305) NFSMounts: NFSv4Mounts: /common/home communis.lcsr.rutgers.edu:/common/home nfs4 rw,nosuid,nodev,relatime,vers=4.2,rsize=65536,wsize=393216,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=krb5,clientaddr=128.6.60.252,local_lock=none,addr=172.17.11.218 SourcePackage: nfs-utils SyslogNFS: Mar 05 13:28:08 basel.cs.rutgers.edu rpc.gssd[11676]: event_dispatch() returned 0! Mar 06 09:51:57 basel.cs.rutgers.edu rpc.statd[37785]: Version 2.6.3 starting Mar 06 09:51:57 basel.cs.rutgers.edu rpc.statd[37785]: Flags: TI-RPC Mar 06 09:51:57 basel.cs.rutgers.edu rpc.statd[37785]: Failed to read /var/lib/nfs/state: Success Mar 06 09:51:57 basel.cs.rutgers.edu rpc.statd[37785]: Initializing NSM state UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.nfs-common: 2024-03-05T13:25:47.124322 ** Affects: nfs-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble regression-release ** Tags added: regression-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056335 Title: /etc/nfsmount.conf doesn't work for servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2056335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056217] Re: nmcli regression: can't set IPV6 token
** Tags added: regression-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056217 Title: nmcli regression: can't set IPV6 token To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2056217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056217] [NEW] nmcli regression: can't set IPV6 token
Public bug reported: 24.04 nightly, downloaded Mar 5. network-manager 1.45.90-1ubuntu1 In network manager, if you try to set ipv6.token, when you save it says Error: connection verification failed: ipv6.token: only makes sense with EUI64 address generation mode This is the same as under 22.04. However under 22.04 the solution is setipv6.addr-gen-mode eui64 along with the token. In 24.04 when you save you get Error: Failed to save 'netplan-enp3s0' (6effa1b1-280b-3785-9b52-c723b445fb3e) connection: failed to update connection: netplan: YAML translation failed: Error in network definition: enp3s0: ipv6-address-generation and ipv6-address-token are mutually exclusive There doesn't seem to be any combination involving the token that works. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass Date: Tue Mar 5 14:14:01 2024 InstallationDate: Installed on 2024-03-05 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240305) IpRoute: default via 128.6.60.1 dev enp3s0 proto dhcp src 128.6.60.252 metric 100 128.6.60.0/24 dev enp3s0 proto kernel scope link src 128.6.60.252 metric 100 IwConfig: lono wireless extensions. enp3s0no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH enp3s0 ethernet connected full limited /org/freedesktop/NetworkManager/Devices/2 netplan-enp3s0 6effa1b1-280b-3785-9b52-c723b445fb3e /org/freedesktop/NetworkManager/ActiveConnection/2 lo loopback connected (externally) unknown unknown /org/freedesktop/NetworkManager/Devices/1 lo b04a6583-06fa-4685-bbd9-05171997cf93 /org/freedesktop/NetworkManager/ActiveConnection/1 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.45.90 connected started full enabled missing enabled missing enabled ** Affects: network-manager (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/2056217 Title: nmcli regression: can't set IPV6 token To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2056217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2044657] Re: Multiple data corruption issues in zfs
Since I was just referenced, note that I wouldn't favor putting 2.2 into Jammy. I would, however, prefer to see the latest 2.1.x. 2.2 is still seeing a substantial number of bug fixes. It will probably be ok by the release date of 24.04, but I still wouldn't change major versions for Jammy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: Multiple data corruption issues in zfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055211] Re: apt show marsshooter Homepage 404's if you right click and open link
Better to change the URL to the homepage listed on the above site, which is: https://sourceforge.net/projects/mars-game/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055211 Title: apt show marsshooter Homepage 404's if you right click and open link To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marsshooter/+bug/2055211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055211] [NEW] apt show marsshooter Homepage 404's if you right click and open link
Public bug reported: apt show marsshooter Homepage: https://github.com/thelaui/M.A.R.S. Note: the homepage listed above works if you type it into a web browser with the period, but if you right click and select open link (at least in Xubuntu) it opens as: https://github.com/thelaui/M.A.R.S (missing the . at the end) This probably doesn't need changing as most people who know apt show might figure out the URL... but it's messy and probably a URL shortener or redirect to the page would be better. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: marsshooter (not installed) ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue Feb 27 14:26:39 2024 InstallationDate: Installed on 2024-01-25 (33 days ago) InstallationMedia: Xubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: marsshooter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: marsshooter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055211 Title: apt show marsshooter Homepage 404's if you right click and open link To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marsshooter/+bug/2055211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055188] [NEW] Apt show gnome-breakout Homepage URL redirects to End of Life web space
Public bug reported: apt show gnome-breakout Homepage: www.users.on.net/~mipearson/ Clicking on the link redirects to https://www.internode.on.net/nodesupport/guides/internode_members_webspace_end_of_life The host has stopped providing free webspace. Description:Ubuntu 22.04.4 LTS gnome-breakout: Installed: (none) Candidate: 0.5.3-7build1 Version table: 0.5.3-7build1 500 500 http://ca.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages Just remove the Homepage, or maybe link to: https://launchpad.net/ubuntu/+source/gnome-breakout ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-breakout (not installed) ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue Feb 27 10:41:14 2024 InstallationDate: Installed on 2024-01-25 (32 days ago) InstallationMedia: Xubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-breakout UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-breakout (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055188 Title: Apt show gnome-breakout Homepage URL redirects to End of Life web space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-breakout/+bug/2055188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055174] [NEW] Apt show njam Homepage URL (a sourceforge URL) redirects to a site that doesn't exist.
Public bug reported: sudo apt show njam Homepage: http://njam.sourceforge.net Clicking on this link redirects to https://domyjavaassignment.com/writer.html, which is a server not found error. [lsb_release -rd] Description:Ubuntu 22.04.4 LTS [apt-cache policy njam] njam: Installed: (none) Candidate: 1.25-11fakesync1 Version table: 1.25-11fakesync1 500 500 http://ca.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages Just remove the redirected link or update the package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: njam (not installed) ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue Feb 27 09:41:55 2024 InstallationDate: Installed on 2024-01-25 (32 days ago) InstallationMedia: Xubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: njam UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: njam (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055174 Title: Apt show njam Homepage URL (a sourceforge URL) redirects to a site that doesn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/njam/+bug/2055174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003588] Re: CVE 2022-4378 fix is in Kinetic, needed on Lunar
Because it is not production ready, We use the livecd uninstalled. Please make an exception for the kernel packages, Please just put the kinetic kernels on the lunar livecds, (And for all new) So we dont have to roll our own livecd just to smoke test a new version, So we dont get the avalanche of failures like our recent move to jammy. Without the kernel package I have not found it practical to try lunar (and all new) online at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2003588 Title: CVE 2022-4378 fix is in Kinetic, needed on Lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972749] Re: Logging into a second Wayland session/user doesn't work [Failed to start X Wayland: Wrong ownership for directory "/tmp/.X11-unix"]
After further investigation, I found the source of my issue. Basically the / directory had the wrong ownership. Not sure how I did that but it seemed to have the side-effect of making systemd-tmpfiles not create directories as it should. I saw messages like this in the log that clued me in. May 09 21:11:49 x1 systemd-tmpfiles[1665]: Detected unsafe path transition / (owned by charles) → /tmp (owned by root) during canonicalization of /tmp. After a chown, ls -ld / now shows ownership by root:root correctly and I no longer get errors in the log. Note this file is what creates the directories root@x1:~# cat /lib/tmpfiles.d/x11.conf # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. # See tmpfiles.d(5) for details # Make sure these are created by default so that nobody else can # or empty them at startup D! /tmp/.X11-unix 1777 root root 10d D! /tmp/.ICE-unix 1777 root root 10d D! /tmp/.XIM-unix 1777 root root 10d D! /tmp/.font-unix 1777 root root 10d D! /tmp/.Test-unix 1777 root root 10d # Unlink the X11 lock files r! /tmp/.X[0-9]*-lock And this helped me figure out the issue journalctl -xe -u systemd-tmpfiles-setup.service Thanks for looking into it, sorry for the bug report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972749 Title: Logging into a second Wayland session/user doesn't work [Failed to start X Wayland: Wrong ownership for directory "/tmp/.X11-unix"] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1972749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972749] Re: Multiple Xsessions doesn't work
chown root:root /tmp/.X11-unix/ chown root:root /tmp/.ICE-unix/ Fixes the issue. I see there's a masked x11-common service that seems to set permissions on these directories. Not sure how these directories are supposed to be created and why that's going wrong. I ran /etc/init.d/x11-common start manually and it set the ownership to gdm instead of root which also seems to be wrong. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972749 Title: Multiple Xsessions doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1972749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972749] [NEW] Multiple Xsessions doesn't work
Public bug reported: On my system with Nvidia 510 drivers I found that if I'm logged in and lock the session another user can't login. I reset the 2nd user's account to verify that if I login and lock my session they can't login. I found this in permission error in the logs. May 09 21:58:20 x1 gnome-shell[17718]: Failed to start X Wayland: Wrong ownership for directory "/tmp/.X11-unix" I've confirmed that /tmp/.X11-unix is owned by the 1st user, so something seems to be causing the system to use the same tmp directory for both users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 9 22:14:43 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/510.60.02, 5.15.0-27-generic, x86_64: installed nvidia/510.60.02, 5.17.6, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER] [10de:2187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1650 SUPER] [1458:401a] MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vg-root ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1205 dmi.board.asset.tag: Default string dmi.board.name: PRIME H270-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1205:bd05/11/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH270-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug crash jammy ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972749 Title: Multiple Xsessions doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1972749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970050] Re: [H97M-HD3, Intel Haswell HDMI, Digital Out, HDMI] No sound at all because of upgrade from 20.04 LTS to 22.04
I have an Intel Nuc, Product Name: D34010WYK, i3-4010U, its hooked up a Samsung TV via hdmi. The sound defaults to HDMI/DisplayPort - Built-in Audio, Digital Stereo (HDMI) Output but that doesn't work. If I flip it to Digital Surround it works but since the TV only has a left/right speaker I would think stereo should work and doesn't. I confirmed the issue is the same if I boot off the desktop ISO and "Try Ubuntu", since I upgraded my system I thought maybe something wasn't right because of that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970050 Title: [H97M-HD3, Intel Haswell HDMI, Digital Out, HDMI] No sound at all because of upgrade from 20.04 LTS to 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1970050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948626] Re: Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010
Jeff, The patches are queued up to be submitted to 5.18 https://git.infradead.org/git/nvme.git/log/refs/tags/nvme-5.18-2022-03-03 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948626 Title: Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956787] Re: nfs v3 locking fails - rpc-statd not started after minor upgrade
Also, can I interest you in 1918312 for 22.04? Everyone agrees it's a security issue. It has a well-known 2-line fix (our version is 4 lines), which we've been using in production for over a year. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956787 Title: nfs v3 locking fails - rpc-statd not started after minor upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1956787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956787] Re: nfs v3 locking fails - rpc-statd not started after minor upgrade
That's a sensible approach, but there are loads of web pages telling people how to set up NFS, and they all claim that on current distributions you no longer need to enable individual services. That's not true for Ubuntu 20. Please do make sure it's fix in 22.04. The original reasoning had a hole in it: with the scripts, there were three states: on, off, and default. Default was on. With the patch the default is off. I see no way in systemd to duplicate the way the scripts worked purely within systemd. This problem is particularly insidious. First, the symptoms aren't obvious. It took us a couple of days to figure out what was going on. Second, the problem doesn't occur if you mount anything by NFS3. So things worked in testing, but failed the first time we rebooting in production. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956787 Title: nfs v3 locking fails - rpc-statd not started after minor upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1956787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956787] Re: nfs v3 locking fails - rpc-statd not started after minor upgrade
I conjecture that the problem occurred when moving from init scripts to systemd. It's pretty clear that the default in the nfs-common init script was to start statd. I conjecture that when converting to systemd, someone forgot to put a Wants in nfs-server. It's got an after but not a Wants. Writing the unit file with an [Install] section implies an explicit enable, but you probably don't want that. You probably want nfs-server to start it. It wouldn't be easy to start it the first time a client mounts via NFS 3, without a kernel upcall, so I think nfs-common was right to default to using it. But it looks like nfs-common is a vestige of the init script days and isn't used except in single user. For what it's worth, centos 7 has a nearly identical unit file for rpc- statd, except it's missing the [Install] section (presumably because it's intended to be invoked by other things and not explicitly enabled). There are Wants for autofs and nfs-server. I think adding Wants to at least nfs-server makes sense. rpc-statd.service doesn't have an install section -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956787 Title: nfs v3 locking fails - rpc-statd not started after minor upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1956787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956787] Re: nfs v3 locking fails - rpc-statd not started after minor upgrade
Statd is used by both client and server. I think that note is for the client usage. Our servers don't necessariy do any NFS3 client mounts, so the client start would't happen. Is it possible that at some point I mounted something via NFS3 and that's the only reason statd was running? I can't prove that that isn't true. I tried enabling nfs-server and that didn't help. My solution has been to enable rpc-statd explicitly. That works. The reason I reported the problem is that it had previously worked automatically, and it took me quite a while to figure out why after the upgrade NFS 3 wasn't working on the server. I might not be alone in this. It looks like it's supposed to be started by /etc/init.d/nfs-common, but I'm pretty sure that isn't started except in /etc/rcS.d/, which wouldn't normally happen. I put a statement in nfs-common to create a file in /var/log, and it didn't happen, so I don't believe nfs-common ran. I suspect statd should be started as part of nfs-server, but it doesn't seem to be happening. Unless you assume that people are just using nfs 4 and want to require manual intervention to support 3. I wouldn't expect that. Particularly since the symptoms are subtle. If you try an NFS 3 mount it works. Things don't start failing until someone tries locking. The most common case is probably firefox, thunderbird, etc, which lock their profiles. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956787 Title: nfs v3 locking fails - rpc-statd not started after minor upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1956787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956787] Re: nfs v3 locking fails - rpc-statd not started after minor upgrade
right. It's not failing. It's not running at all.
systemctl status rpc-statd
● rpc-statd.service - NFS status monitor for NFSv2/3 locking.
Loaded: loaded (/lib/systemd/system/rpc-statd.service; disabled; vendor
preset: enabled)
Active: inactive (dead)
Journalctl doesn't show that nfs-utils ran. As far as I can tell, that's
the only thing that would activate it.
I note that there's an [Install] section in rpc-statd.service. That
implies that it's intended to be enabled. It's not. If you enable it,
everything works. I suspected maybe the upgrade was supposed to enable
it but didn't.
rpc.statd version 1.3.3
ls -l /sbin/rpc.statd
-rwxr-xr-x 1 root root 89016 May 24 2021 /sbin/rpc.statd
ls -lc /sbin/rpc.statd
-rwxr-xr-x 1 root root 89016 Jan 10 15:09 /sbin/rpc.statd
It looks like it changed in the last update. It was "apt upgrade"
/etc/default/nfs-common
STATDOPTS=
NEED_GSSD=yes
/etc/default/nfs-kernel-server
RPCNFSDCOUNT=8
RPCNFSDPRIORITY=0
RPCMOUNTDOPTS="--manage-gids"
NEED_SVCGSSD="yes"
RPCSVCGSSDOPTS=""
/etc/default/rpcbind
OPTIONS=""
OPTIONS="-w"
/etc/systemd/system/rpc-gssd.service.d
gss-krb.conf
[Service]
Environment=KRB5_CONFIG=/etc/krb5.conf:/etc/krb5.conf.gssd
time.conf
[Service]
Environment=GSSDARGS=-t600
The KRB5_CONFIG is to configure
[plugins]
ccselect = {
module = nfs:/usr/lib/ccselect_nfs.so
}
ccselect_nfs.so selects the user's primary principal, so that if they've done
kinit as user.admin to do privileged stuff, NFS still uses their default
principal.
Note that this was all working before the upgrade. The upgrade was
2022-01-10 15:09:15
Looks like the system was installed July 31, 2020, and no upgrades other
than unattended upgrade since then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956787
Title:
nfs v3 locking fails - rpc-statd not started after minor upgrade
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1956787/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956787] Re: nfs v3 locking fails - rpc-statd not started after minor upgrade
** Summary changed: - nfs v3 locking fails - 5.4.0-92 regression + nfs v3 locking fails - rpc-statd not started after minor upgrade ** Package changed: kernel-package (Ubuntu) => nfs-utils (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956787 Title: nfs v3 locking fails - rpc-statd not started after minor upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1956787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956787] Re: nfs v3 locking fails - 5.4.0-92 regression
It has nothing to do with the kernel. For some reasons rpc.statd isn't getting started. The systemd declaration looks fine, but it isn't there. Doing "systemctl start rpc-statd" and "enable" fixes it. The other parts of nfs-utils seem fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956787 Title: nfs v3 locking fails - 5.4.0-92 regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1956787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956787] Re: nfs v3 locking fails - 5.4.0-92 regression
The problem occurs on 4 different servers. It does not occur on a server running Centos7 updated to kernel 5.4.170. This implies that the problem is most likely an Ubuntu patch (or it was fixed upstream between 5.4.157 and 5.4.170). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956787 Title: nfs v3 locking fails - 5.4.0-92 regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1956787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956787] Re: nfs v3 locking fails - 5.4.0-92 regression
** Summary changed: - nfs v3 locking fails + nfs v3 locking fails - 5.4.0-92 regression -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956787 Title: nfs v3 locking fails - 5.4.0-92 regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1956787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956787] Re: nfs v3 locking fails
Also, "lslocks" on the server shows no locks associated with lockd, though there are locks associated with nfsd. (nfsd would be locks from NFS 4 I believe.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956787 Title: nfs v3 locking fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1956787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956787] [NEW] nfs v3 locking fails
Public bug reported: We just upgraded our nfs servers from 5.4.0-72 to 5.4.0-92. We are using NFS v3 in a large computer science department, with several hundred clients. Lots of applications are now failing because locks don't work. /var/log/syslog on the client reports lockd not responding. tcpdump shows that the client tries to connect to lockd but there is no response to the TCP SYN. netstat on the server shows some connections open, with lots of bytes in the receive queue. The problem probably occurs only with lots of clients. I believe any typical test would work fine. The problem is new. That is, it didn't happen in 5.4.0-72. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: kernel-common (not installed) ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 Uname: Linux 5.4.0-92-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jan 7 13:07:34 2022 InstallationDate: Installed on 2020-10-14 (450 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: kernel-package UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-10-14T13:53:33.474467 ** Affects: kernel-package (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956787 Title: nfs v3 locking fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1956787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905468] Re: Ubuntu 20.04LTS vtund program fails to function
Confirming this same error on a fresh install of 20.04 LTS as well -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905468 Title: Ubuntu 20.04LTS vtund program fails to function To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vtun/+bug/1905468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1953524] Re: Upgrade 20.04 to 21.10
Brian Have you been able to make any progress? I dont understand as any further install I still get the same error when I run sudo apt-get install -f: dpkg-maintscript-helper: error: file '/usr/share/npm/node_modules/node-gyp' not owned by package 'npm:all' Do I have to change the owner and group of /usr/share/npm/node_modules/node-gyp to nmp:all, I thought with sudo it should work. I cant even build java apps using gradle. This is a real blocker, do I have to now do a clean ubuntu install? Regards Charlie Simms On Wed, 8 Dec 2021 at 16:35, Brian Murray <1953...@bugs.launchpad.net> wrote: > The following lines in VarLogDistUpgradeApttermlog.txt indicate where > part of the problem is: > > Preparing to unpack .../npm_7.5.2+ds-1_all.deb ...^M > dpkg-maintscript-helper: error: file > '/usr/share/npm/node_modules/node-gyp' not owned by package 'npm:all'^M > dpkg-maintscript-helper: error: file > '/usr/share/npm/node_modules/node-gyp/gyp' not owned by package 'npm:all'^M > dpkg-maintscript-helper: error: file > '/usr/share/npm/node_modules/node-gyp/gyp/pylib' not owned by package > 'npm:all'^M > dpkg-maintscript-helper: error: file > '/usr/share/npm/node_modules/node-gyp/gyp/pylib/gyp' not owned by package > 'npm:all'^M > dpkg-maintscript-helper: error: file > '/usr/share/npm/node_modules/node-gyp/gyp/pylib/gyp/generator' not owned by > package 'npm:all'^M > dpkg-maintscript-helper: error: file > '/usr/share/npm/node_modules/node-gyp/gyp/pylib/gyp/generator/make.pyc' not > owned by package 'npm:all'^M > dpkg-maintscript-helper: error: file > '/usr/share/npm/node_modules/node-gyp/gyp/pylib/gyp/generator/__init__.pyc' > not owned by package 'npm:all'^M > dpkg-maintscript-helper: error: file > '/usr/share/npm/node_modules/node-gyp/gyp/pylib/gyp/input.pyc' not owned by > package 'npm:all'^M > dpkg-maintscript-helper: error: file > '/usr/share/npm/node_modules/node-gyp/gyp/pylib/gyp/common.pyc' not owned > by package 'npm:all'^M > dpkg-maintscript-helper: error: file > '/usr/share/npm/node_modules/node-gyp/gyp/pylib/gyp/simple_copy.pyc' not > owned by package 'npm:all'^M > dpkg-maintscript-helper: error: file > '/usr/share/npm/node_modules/node-gyp/gyp/pylib/gyp/__init__.pyc' not owned > by package 'npm:all'^M > dpkg-maintscript-helper: error: file > '/usr/share/npm/node_modules/node-gyp/gyp/pylib/gyp/xcode_emulation.pyc' > not owned by package 'npm:all'^M > dpkg-maintscript-helper: error: directory '/usr/share/npm' contains files > not owned by package npm:all, cannot switch to symlink^M > dpkg: error processing archive > /var/cache/apt/archives/npm_7.5.2+ds-1_all.deb (--unpack):^M > new npm package pre-installation script subprocess returned error exit > status 1^M > Errors were encountered while processing:^M > /var/cache/apt/archives/npm_7.5.2+ds-1_all.deb^M > > However, looking at VarLogDistUpgradeAptclone the package node-gyp > (which I'm guessing owns those files) is the official one from the > Ubuntu archive for Focal. > > The file /var/log/dist-upgrade/main.log from your upgrade attempt would > be helpful in further figuring out what went wrong. The folder > /var/log/dist-upgrade/ contains folders for the date and times an > upgrade was attempted or made so if you don't find it in the root > directory look in a folder like '20211207-1234'. > > ** Changed in: ubuntu-release-upgrader (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1953524 > > Title: > Upgrade 20.04 to 21.10 > > Status in ubuntu-release-upgrader package in Ubuntu: > Incomplete > > Bug description: > I ran the installation to upgrade using > https://help.ubuntu.com/community/ImpishUpgrades > section:- Upgrading Ubuntu Desktops to 21.10 > but got the following message: > The upgrade will continue but the > '/tmp/apt-dpkg-install-ZM0HnK/0993-npm_7.5.2+ds-1_all.deb' package may not > be in a working state. Please consider submitting a bug report about it. > > Now I cant upgrade using the software updater I get the following error > The package system is broken > If you are using third party repositories then disable them, since they > are a common source of problems. > Now run the following command in a terminal: apt-get install -f > Transaction failed: The package system is broken >The following packages have unmet dependencies: > node-mkdirp: > --- > ProblemType: Bug > ApportVersion: 2.20.11-0ubuntu65.4 > Architecture: amd64 > CasperMD5CheckResult: unknown > CrashDB: ubuntu > CurrentDesktop: ubuntu:GNOME > DistributionChannelDescriptor: ># This is a distribution channel descriptor ># For more information see > http://wiki.ubuntu.com/DistributionChannelDescriptor >canonical-oem-somerville-xenial-amd64-20160624-2 > DistroRelease: Ubuntu 21.04 > EcryptfsInUse: Yes > InstallationDate: Installed on 2017-11-12 (1486 days ago) > InstallationMedia: Ubuntu
[Bug 1953524] Re: Upgrade 20.04 to 21.10
Brian I have attached /var/log/dist-upgrade/20211207-0850 and 20211207-0819 which have the log file requested. Many thanks Charlie Simms On Wed, 8 Dec 2021 at 16:35, Brian Murray <1953...@bugs.launchpad.net> wrote: > The following lines in VarLogDistUpgradeApttermlog.txt indicate where > part of the problem is: > > Preparing to unpack .../npm_7.5.2+ds-1_all.deb ...^M > dpkg-maintscript-helper: error: file > '/usr/share/npm/node_modules/node-gyp' not owned by package 'npm:all'^M > dpkg-maintscript-helper: error: file > '/usr/share/npm/node_modules/node-gyp/gyp' not owned by package 'npm:all'^M > dpkg-maintscript-helper: error: file > '/usr/share/npm/node_modules/node-gyp/gyp/pylib' not owned by package > 'npm:all'^M > dpkg-maintscript-helper: error: file > '/usr/share/npm/node_modules/node-gyp/gyp/pylib/gyp' not owned by package > 'npm:all'^M > dpkg-maintscript-helper: error: file > '/usr/share/npm/node_modules/node-gyp/gyp/pylib/gyp/generator' not owned by > package 'npm:all'^M > dpkg-maintscript-helper: error: file > '/usr/share/npm/node_modules/node-gyp/gyp/pylib/gyp/generator/make.pyc' not > owned by package 'npm:all'^M > dpkg-maintscript-helper: error: file > '/usr/share/npm/node_modules/node-gyp/gyp/pylib/gyp/generator/__init__.pyc' > not owned by package 'npm:all'^M > dpkg-maintscript-helper: error: file > '/usr/share/npm/node_modules/node-gyp/gyp/pylib/gyp/input.pyc' not owned by > package 'npm:all'^M > dpkg-maintscript-helper: error: file > '/usr/share/npm/node_modules/node-gyp/gyp/pylib/gyp/common.pyc' not owned > by package 'npm:all'^M > dpkg-maintscript-helper: error: file > '/usr/share/npm/node_modules/node-gyp/gyp/pylib/gyp/simple_copy.pyc' not > owned by package 'npm:all'^M > dpkg-maintscript-helper: error: file > '/usr/share/npm/node_modules/node-gyp/gyp/pylib/gyp/__init__.pyc' not owned > by package 'npm:all'^M > dpkg-maintscript-helper: error: file > '/usr/share/npm/node_modules/node-gyp/gyp/pylib/gyp/xcode_emulation.pyc' > not owned by package 'npm:all'^M > dpkg-maintscript-helper: error: directory '/usr/share/npm' contains files > not owned by package npm:all, cannot switch to symlink^M > dpkg: error processing archive > /var/cache/apt/archives/npm_7.5.2+ds-1_all.deb (--unpack):^M > new npm package pre-installation script subprocess returned error exit > status 1^M > Errors were encountered while processing:^M > /var/cache/apt/archives/npm_7.5.2+ds-1_all.deb^M > > However, looking at VarLogDistUpgradeAptclone the package node-gyp > (which I'm guessing owns those files) is the official one from the > Ubuntu archive for Focal. > > The file /var/log/dist-upgrade/main.log from your upgrade attempt would > be helpful in further figuring out what went wrong. The folder > /var/log/dist-upgrade/ contains folders for the date and times an > upgrade was attempted or made so if you don't find it in the root > directory look in a folder like '20211207-1234'. > > ** Changed in: ubuntu-release-upgrader (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1953524 > > Title: > Upgrade 20.04 to 21.10 > > Status in ubuntu-release-upgrader package in Ubuntu: > Incomplete > > Bug description: > I ran the installation to upgrade using > https://help.ubuntu.com/community/ImpishUpgrades > section:- Upgrading Ubuntu Desktops to 21.10 > but got the following message: > The upgrade will continue but the > '/tmp/apt-dpkg-install-ZM0HnK/0993-npm_7.5.2+ds-1_all.deb' package may not > be in a working state. Please consider submitting a bug report about it. > > Now I cant upgrade using the software updater I get the following error > The package system is broken > If you are using third party repositories then disable them, since they > are a common source of problems. > Now run the following command in a terminal: apt-get install -f > Transaction failed: The package system is broken >The following packages have unmet dependencies: > node-mkdirp: > --- > ProblemType: Bug > ApportVersion: 2.20.11-0ubuntu65.4 > Architecture: amd64 > CasperMD5CheckResult: unknown > CrashDB: ubuntu > CurrentDesktop: ubuntu:GNOME > DistributionChannelDescriptor: ># This is a distribution channel descriptor ># For more information see > http://wiki.ubuntu.com/DistributionChannelDescriptor >canonical-oem-somerville-xenial-amd64-20160624-2 > DistroRelease: Ubuntu 21.04 > EcryptfsInUse: Yes > InstallationDate: Installed on 2017-11-12 (1486 days ago) > InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary > 20160624-10:47 > Package: ubuntu-release-upgrader (not installed) > ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 > RebootRequiredPkgs: Error: path contained symlinks. > Tags: hirsute dist-upgrade > Uname: Linux 5.4.0-91-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm
Re: [Bug 1953524] Re: Upgrade 20.04 to 21.10
Chris Thank you for your response. I have ran apport-collect 1953524 which has updated my bug in launchpad. Yes I was trying to upgrade to 21.04. Regards Charlie Simms On Wed, 8 Dec 2021 at 01:41, Chris Guiver <1953...@bugs.launchpad.net> wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. Please execute the following command only once, as it > will automatically gather debugging information, in a terminal: > > apport-collect 1953524 > > When reporting bugs in the future please use apport by using 'ubuntu- > bug' and the name of the package affected. You can learn more about this > functionality at https://wiki.ubuntu.com/ReportingBugs. > > > (are you sure you were upgrading from 20.04 to 21.10? The current > procedure will upgrade you from 20.04 to 21.04 (ie. next supported release) > which matches the package you mention, ie. `npm | 7.5.2+ds-1 | > hirsute/universe| source, all`) > > I've marked this incomplete as no details were provided; you can change > status back to "New" after running apport-collect. > > Bug reporting is mostly about finding & fixing problems thus preventing > future users from hitting the same bug. > > I suspect a Support site would be more appropriate, eg. > https://answers.launchpad.net/ubuntu. You can also find help with your > problem in the support forum of your local Ubuntu community > http://loco.ubuntu.com/ or asking at https://askubuntu.com or > https://ubuntuforums.org, or for more support options please look at > https://discourse.ubuntu.com/t/community-support/709 > > > ** Changed in: ubuntu-release-upgrader (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1953524 > > Title: > Upgrade 20.04 to 21.10 > > Status in ubuntu-release-upgrader package in Ubuntu: > Incomplete > > Bug description: > I ran the installation to upgrade using > https://help.ubuntu.com/community/ImpishUpgrades > section:- Upgrading Ubuntu Desktops to 21.10 > but got the following message: > The upgrade will continue but the > '/tmp/apt-dpkg-install-ZM0HnK/0993-npm_7.5.2+ds-1_all.deb' package may not > be in a working state. Please consider submitting a bug report about it. > > Now I cant upgrade using the software updater I get the following error > The package system is broken > If you are using third party repositories then disable them, since they > are a common source of problems. > Now run the following command in a terminal: apt-get install -f > Transaction failed: The package system is broken >The following packages have unmet dependencies: > node-mkdirp: > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1953524/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953524 Title: Upgrade 20.04 to 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1953524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953524] VarLogDistupgradeLspcitxt.txt
apport information ** Attachment added: "VarLogDistupgradeLspcitxt.txt" https://bugs.launchpad.net/bugs/1953524/+attachment/5546144/+files/VarLogDistupgradeLspcitxt.txt ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953524 Title: Upgrade 20.04 to 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1953524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953524] VarLogDistupgradeApttermlog.txt
apport information ** Attachment added: "VarLogDistupgradeApttermlog.txt" https://bugs.launchpad.net/bugs/1953524/+attachment/5546143/+files/VarLogDistupgradeApttermlog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953524 Title: Upgrade 20.04 to 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1953524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953524] VarLogDistupgradeAptlog.txt
apport information ** Attachment added: "VarLogDistupgradeAptlog.txt" https://bugs.launchpad.net/bugs/1953524/+attachment/5546142/+files/VarLogDistupgradeAptlog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953524 Title: Upgrade 20.04 to 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1953524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953524] VarLogDistupgradeAptclonesystemstate.tar.gz
apport information ** Attachment added: "VarLogDistupgradeAptclonesystemstate.tar.gz" https://bugs.launchpad.net/bugs/1953524/+attachment/5546141/+files/VarLogDistupgradeAptclonesystemstate.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953524 Title: Upgrade 20.04 to 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1953524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953524] Re: Upgrade 20.04 to 21.10
apport information ** Tags added: apport-collected dist-upgrade hirsute ** Description changed: I ran the installation to upgrade using https://help.ubuntu.com/community/ImpishUpgrades section:- Upgrading Ubuntu Desktops to 21.10 but got the following message: The upgrade will continue but the '/tmp/apt-dpkg-install-ZM0HnK/0993-npm_7.5.2+ds-1_all.deb' package may not be in a working state. Please consider submitting a bug report about it. Now I cant upgrade using the software updater I get the following error The package system is broken If you are using third party repositories then disable them, since they are a common source of problems. Now run the following command in a terminal: apt-get install -f Transaction failed: The package system is broken The following packages have unmet dependencies: node-mkdirp: + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu65.4 + Architecture: amd64 + CasperMD5CheckResult: unknown + CrashDB: ubuntu + CurrentDesktop: ubuntu:GNOME + DistributionChannelDescriptor: + # This is a distribution channel descriptor + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-xenial-amd64-20160624-2 + DistroRelease: Ubuntu 21.04 + EcryptfsInUse: Yes + InstallationDate: Installed on 2017-11-12 (1486 days ago) + InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 + Package: ubuntu-release-upgrader (not installed) + ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 + RebootRequiredPkgs: Error: path contained symlinks. + Tags: hirsute dist-upgrade + Uname: Linux 5.4.0-91-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dip docker lpadmin plugdev pulse pulse-access root sambashare sudo video wireshark + VarLogDistupgradeTermlog: + + _MarkForUpload: True ** Attachment added: "CurrentDmesg.txt.txt" https://bugs.launchpad.net/bugs/1953524/+attachment/5546137/+files/CurrentDmesg.txt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953524 Title: Upgrade 20.04 to 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1953524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953524] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1953524/+attachment/5546138/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953524 Title: Upgrade 20.04 to 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1953524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953524] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1953524/+attachment/5546139/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953524 Title: Upgrade 20.04 to 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1953524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953524] VarLogDistupgradeAptHistorylog.txt
apport information ** Attachment added: "VarLogDistupgradeAptHistorylog.txt" https://bugs.launchpad.net/bugs/1953524/+attachment/5546140/+files/VarLogDistupgradeAptHistorylog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953524 Title: Upgrade 20.04 to 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1953524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953524] [NEW] Upgrade 20.04 to 21.10
Public bug reported: I ran the installation to upgrade using https://help.ubuntu.com/community/ImpishUpgrades section:- Upgrading Ubuntu Desktops to 21.10 but got the following message: The upgrade will continue but the '/tmp/apt-dpkg-install-ZM0HnK/0993-npm_7.5.2+ds-1_all.deb' package may not be in a working state. Please consider submitting a bug report about it. Now I cant upgrade using the software updater I get the following error The package system is broken If you are using third party repositories then disable them, since they are a common source of problems. Now run the following command in a terminal: apt-get install -f Transaction failed: The package system is broken The following packages have unmet dependencies: node-mkdirp: ** Affects: ubuntu-release-upgrader (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/1953524 Title: Upgrade 20.04 to 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1953524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949647] Re: When changing the driver for any printer the driver program just continues searching infinitely
*** This bug is a duplicate of bug 1883370 *** https://bugs.launchpad.net/bugs/1883370 ** This bug has been marked a duplicate of bug 1883370 system-config-printer hangs when trying to change driver -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949647 Title: When changing the driver for any printer the driver program just continues searching infinitely To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1949647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949647] [NEW] When changing the driver for any printer the driver program just continues searching infinitely
Public bug reported: Description:Ubuntu 20.04.3 LTS Release:20.04 system-config-printer: Installed: 1.5.12-0ubuntu1.1 Candidate: 1.5.12-0ubuntu1.1 Version table: *** 1.5.12-0ubuntu1.1 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.5.12-0ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://ca.archive.ubuntu.com/ubuntu focal/main i386 Packages I first experienced this at work on an Asus machine with an i7-3770 CPU, 16GB of RAM. I connected an HP Laserjet 1020. Xubuntu appeared to configure and install a driver, but wouldn't print a test page. (Not an issue with other printers on the same system) So I tried changing the Make and Model of the printer. When I clicked Change beside the Make and Model dialog box the Change Driver "Searching" dialog appeared, but it just sits infinitely looking for drivers. I thought it might be some odd relationship between the machine and printer so I tried a different system at work and a different printer (a brother printer which Xubuntu found and printing worked). Same issue trying to change the Make and Model. Also tried at home thinking it might be an issue with our PXE installed Xubuntu, but same issue (USB installed). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: system-config-printer 1.5.12-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Nov 3 19:14:48 2021 ExecutablePath: /usr/share/system-config-printer/system-config-printer.py InterpreterPath: /usr/bin/python3.8 Lpstat: device for DYMO-LabelWriter-450: usb://DYMO/LabelWriter%20450?serial=01010112345600 MachineType: To be filled by O.E.M. To be filled by O.E.M. PackageArchitecture: all Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/DYMO-LabelWriter-450.ppd'] failed with exit code 2: grep: /etc/cups/ppd/DYMO-LabelWriter-450.ppd: Permission denied ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=3380cfa0-cebe-4249-b891-a500fa13528d ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: system-config-printer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2019 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Intel X79 dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/17/2019:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:skuTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnIntelX79:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. ** Affects: system-config-printer (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/1949647 Title: When changing the driver for any printer the driver program just continues searching infinitely To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1949647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947112] Re: Qasmixer crashes when MIXER Device > arcam-av port is clicked
** Description changed: To reproduce: 1. launch Qasmixer 2. In Mixer Device list, click on 'arcam-av'. - 3. Qasmixer crashes every time. + 3. Qasmixer crashes every time and disappears from the screen. $ ubuntu-bug qasmixer /usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required (got type float). Implicit conversion to integers using __int__ is deprecated, and may be removed in a future version of Python. progress.setValue(value * 1000) ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: qasmixer 0.23.0-1 ProcVersionSignature: Ubuntu 5.13.0-19.19-lowlatency 5.13.14 Uname: Linux 5.13.0-19-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Oct 14 08:16:42 2021 InstallationDate: Installed on 2021-10-07 (6 days ago) InstallationMedia: Ubuntu-Studio 21.10 "Impish Indri" - Beta amd64 (20210923) SourcePackage: qastools UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947112 Title: Qasmixer crashes when MIXER Device > arcam-av port is clicked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qastools/+bug/1947112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947112] [NEW] Qasmixer crashes when MIXER Device > arcam-av port is clicked
Public bug reported: To reproduce: 1. launch Qasmixer 2. In Mixer Device list, click on 'arcam-av'. 3. Qasmixer crashes every time and disappears from the screen. $ ubuntu-bug qasmixer /usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required (got type float). Implicit conversion to integers using __int__ is deprecated, and may be removed in a future version of Python. progress.setValue(value * 1000) ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: qasmixer 0.23.0-1 ProcVersionSignature: Ubuntu 5.13.0-19.19-lowlatency 5.13.14 Uname: Linux 5.13.0-19-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Oct 14 08:16:42 2021 InstallationDate: Installed on 2021-10-07 (6 days ago) InstallationMedia: Ubuntu-Studio 21.10 "Impish Indri" - Beta amd64 (20210923) SourcePackage: qastools UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qastools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Description changed: To reproduce: 1. launch Qasmixer 2. In Mixer Device list, click on 'arcam-av'. - 3. Qasnixer crashes every time. + 3. Qasmixer crashes every time. $ ubuntu-bug qasmixer /usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required (got type float). Implicit conversion to integers using __int__ is deprecated, and may be removed in a future version of Python. - progress.setValue(value * 1000) + progress.setValue(value * 1000) ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: qasmixer 0.23.0-1 ProcVersionSignature: Ubuntu 5.13.0-19.19-lowlatency 5.13.14 Uname: Linux 5.13.0-19-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Oct 14 08:16:42 2021 InstallationDate: Installed on 2021-10-07 (6 days ago) InstallationMedia: Ubuntu-Studio 21.10 "Impish Indri" - Beta amd64 (20210923) SourcePackage: qastools UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - Qasmixer crashes when MIXER > arcam-av port is clicked + Qasmixer crashes when MIXER Device > arcam-av port is clicked -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947112 Title: Qasmixer crashes when MIXER Device > arcam-av port is clicked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qastools/+bug/1947112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946572] Re: Studio controls hangs on Apply
** Description changed: To reproduce: 1. Go to Extra Devices tab. 2. Select 'Nvidia 0,0 capture and playback 0' in Select Device to Edit drop down menu. 3. Click on Capture Port Count minus button to reduce it 0. This causes Studio Controls to hang. The plus and minus boxes are greyed out. [A workaround is to restart Studio Controls which makes the plus and minus buttons available again but this time click on the All/Off toggle. - This reduces the capture port count to 0. Then click more n Apply Audio + This reduces the capture port count to 0. Then click on Apply Audio Settings]. Traceback (most recent call last): File "/usr/bin/studio-controls", line 1039, in xdev_changed sub_db['rate'] = int(self.xdev_rate_drop.get_active_id()) TypeError: int() argument must be a string, a bytes-like object or a number, not 'NoneType' ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: studio-controls 2.2.6-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-lowlatency 5.13.13 Uname: Linux 5.13.0-16-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Oct 9 18:57:30 2021 InstallationDate: Installed on 2021-10-07 (2 days ago) InstallationMedia: Ubuntu-Studio 21.10 "Impish Indri" - Beta amd64 (20210923) PackageArchitecture: all SourcePackage: studio-controls UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946572 Title: Studio controls hangs on Apply To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/studio-controls/+bug/1946572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946572] Re: Studio controls hangs on Apply
** Description changed: + To reproduce: + + 1. Go to Extra Devices tab. + + 2. Select Nvidia 0,0 capture and playback 0' selected in Select Device + to Edit drop down menu. + + 3. Click on Capture Port Count minus button to reduce it 0. This causes + Studio Controls to hang. The plus and minus boxes are greyed out. + + [A workaround is to restart Studio Controls which makes the plus and + minus buttons available again but this time click on the All/Off toggle. + This reduces the capture port count to 0. Then click more n Apply Audio + Settings]. + Traceback (most recent call last): File "/usr/bin/studio-controls", line 1039, in xdev_changed sub_db['rate'] = int(self.xdev_rate_drop.get_active_id()) TypeError: int() argument must be a string, a bytes-like object or a number, not 'NoneType' ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: studio-controls 2.2.6-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-lowlatency 5.13.13 Uname: Linux 5.13.0-16-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Oct 9 18:57:30 2021 InstallationDate: Installed on 2021-10-07 (2 days ago) InstallationMedia: Ubuntu-Studio 21.10 "Impish Indri" - Beta amd64 (20210923) PackageArchitecture: all SourcePackage: studio-controls UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: To reproduce: 1. Go to Extra Devices tab. - 2. Select Nvidia 0,0 capture and playback 0' selected in Select Device - to Edit drop down menu. + 2. Select 'Nvidia 0,0 capture and playback 0' in Select Device to Edit + drop down menu. 3. Click on Capture Port Count minus button to reduce it 0. This causes Studio Controls to hang. The plus and minus boxes are greyed out. [A workaround is to restart Studio Controls which makes the plus and minus buttons available again but this time click on the All/Off toggle. This reduces the capture port count to 0. Then click more n Apply Audio Settings]. Traceback (most recent call last): File "/usr/bin/studio-controls", line 1039, in xdev_changed sub_db['rate'] = int(self.xdev_rate_drop.get_active_id()) TypeError: int() argument must be a string, a bytes-like object or a number, not 'NoneType' ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: studio-controls 2.2.6-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-lowlatency 5.13.13 Uname: Linux 5.13.0-16-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Oct 9 18:57:30 2021 InstallationDate: Installed on 2021-10-07 (2 days ago) InstallationMedia: Ubuntu-Studio 21.10 "Impish Indri" - Beta amd64 (20210923) PackageArchitecture: all SourcePackage: studio-controls UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946572 Title: Studio controls hangs on Apply To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/studio-controls/+bug/1946572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946572] [NEW] Studio controls hangs on Apply
Public bug reported: Traceback (most recent call last): File "/usr/bin/studio-controls", line 1039, in xdev_changed sub_db['rate'] = int(self.xdev_rate_drop.get_active_id()) TypeError: int() argument must be a string, a bytes-like object or a number, not 'NoneType' ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: studio-controls 2.2.6-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-lowlatency 5.13.13 Uname: Linux 5.13.0-16-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Oct 9 18:57:30 2021 InstallationDate: Installed on 2021-10-07 (2 days ago) InstallationMedia: Ubuntu-Studio 21.10 "Impish Indri" - Beta amd64 (20210923) PackageArchitecture: all SourcePackage: studio-controls UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: studio-controls (Ubuntu) Importance: Undecided Status: In Progress ** Tags: amd64 apport-bug impish ** Summary changed: - Studio controls hangs n Apply + Studio controls hangs on Apply -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946572 Title: Studio controls hangs on Apply To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/studio-controls/+bug/1946572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945870] Re: Ardour crashes on launch
Using live USB. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945870 Title: Ardour crashes on launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ardour/+bug/1945870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945870] [NEW] Ardour crashes on launch
Public bug reported: Program crashes on launch. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ardour 1:6.9.0+ds0~ubuntu-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-lowlatency 5.13.13 Uname: Linux 5.13.0-16-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: KDE Date: Sat Oct 2 16:45:03 2021 LiveMediaBuild: Ubuntu-Studio 21.10 "Impish Indri" - Beta amd64 (20210923) SourcePackage: ardour UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ardour (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945870 Title: Ardour crashes on launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ardour/+bug/1945870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1609750]
solved the bug already i cleared some things and made an update On Sun, Sep 26, 2021, 05:40 ian <1609...@bugs.launchpad.net> wrote: > Any update on this? Having issues with sound working for some time, > than suddenly stopping with a buzzing sound. Will attempt to modify > patch for most recent kernel, but my understanding is the kernel should > already be patched. Works fine on galliumos, but not with any other > distro or most recent kernel > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1803810). > https://bugs.launchpad.net/bugs/1609750 > > Title: > Audio not working on Acer Chromebook R11 > > Status in linux: > Confirmed > Status in linux package in Ubuntu: > In Progress > Status in pulseaudio package in Ubuntu: > Invalid > > Bug description: > Audio is not working at all on Acer Chromebook R11 (codename CYAN). > It's a Intel Braswell platform. snd_hda_intel messages seem normal, > but Pulseaudio does not detect sound hardware. > > ProblemType: Bug > DistroRelease: Ubuntu 16.10 > Package: pulseaudio 1:9.0-1.1ubuntu1 > ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 > Uname: Linux 4.4.0-33-generic x86_64 > ApportVersion: 2.20.3-0ubuntu2 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', > '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', > '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', > '/dev/snd/timer'] failed with exit code 1: > CurrentDesktop: Unity > Date: Thu Aug 4 14:12:03 2016 > InstallationDate: Installed on 2016-07-22 (13 days ago) > InstallationMedia: > > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > SourcePackage: pulseaudio > Symptom: audio > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 05/20/2016 > dmi.bios.vendor: coreboot > dmi.chassis.type: 3 > dmi.chassis.vendor: GOOGLE > dmi.modalias: > dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: > dmi.product.name: Cyan > dmi.product.version: 1.0 > dmi.sys.vendor: GOOGLE > --- > ApportVersion: 2.20.3-0ubuntu2 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', > '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', > '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', > '/dev/snd/timer'] failed with exit code 1: > CurrentDesktop: Unity > DistroRelease: Ubuntu 16.10 > HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08 > InstallationDate: Installed on 2016-07-22 (13 days ago) > InstallationMedia: > > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 003: ID 8087:0a2a Intel Corp. >Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: GOOGLE Cyan > Package: linux-image-4.4.0-33-generic 4.4.0-33.52 > PackageArchitecture: amd64 > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic > root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7 > ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > RelatedPackageVersions: >linux-restricted-modules-4.4.0-33-generic N/A >linux-backports-modules-4.4.0-33-generic N/A >linux-firmware1.159 > Tags: yakkety > Uname: Linux 4.4.0-33-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > dmi.bios.date: 05/20/2016 > dmi.bios.vendor: coreboot > dmi.chassis.type: 3 > dmi.chassis.vendor: GOOGLE > dmi.modalias: > dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: > dmi.product.name: Cyan > dmi.product.version: 1.0 > dmi.sys.vendor: GOOGLE > > To manage notifications about this bug go to: > https://bugs.launchpad.net/kernel/+bug/1609750/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609750 Title: Audio not working on Acer Chromebook R11 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1609750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941938] [NEW] systemd trying to unmount non-existent file system
Public bug reported: This output is copied from here: https://github.com/systemd/systemd/issues/20516 because I have not been able to capture the error messages. However what I am seeing is identical. sd-umoun[2406]: Failed to unmount /oldroot: Device or resource busy sd-umoun[2407]: Failed to unmount /oldroot/dev/pts: Device or resource busy sd-umoun[2408]: Failed to unmount /oldroot/dev: Device or resource busy shutdown[1]: Failed to finalize file systems, ignoring This has happened consistently since I upgraded to Ubuntu 20.04 two weeks ago, and is really annoying. Is there an actual problem or is it just noise that can be safely ignored? The only other thing referencing oldroot in its config was snap, which I have completely uninstalled to isolate the problem. /lib/systemd/systemd-shutdown also contains this string: # strings systemd-shutdown |grep old /oldroot sigprocmask(SIG_BLOCK, , ) == 0 sigprocmask(SIG_SETMASK, , NULL) == 0 I have never had an /oldroot mount and there isn't one now. I gather it is something the upgrade process might create, or it could perhaps be something broken in finalrd. Bin Li, who posted the above error to the systemd bug portal, got short shrift there and was told to contact the distro. So I am, as my version of systemd is 245, same as his. This problem is 100% repeateable and I see it every time I shutdown or restart. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Aug 28 14:28:03 2021 InstallationDate: Installed on 2017-05-26 (1554 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 5986:0708 Acer, Inc Integrated Camera Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse 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/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 7: Dev 4, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 7: Dev 4, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: LENOVO 20EVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=3be3-50c9-41cc-94b5-eab06cff1d17 ro quiet splash SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2021-08-05 (22 days ago) dmi.bios.date: 12/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R00ET49W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR00ET49W(1.24):bd12/01/2016:svnLENOVO:pn20EVCTO1WW:pvrThinkPadE560:rvnLENOVO:rn20EVCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E560 dmi.product.name: 20EVCTO1WW dmi.product.sku: LENOVO_MT_20EV_BU_Think_FM_ThinkPad E560 dmi.product.version: ThinkPad E560 dmi.sys.vendor: LENOVO ** Affects: systemd (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/1941938 Title: systemd trying to unmount non-existent file system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1941938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940761] Re: multi-monitor edges still sticky with Sticky Edges turned off
Please close this bug. Found this old thread which still works: https://askubuntu.com/questions/462629/how-to-disable-sticky-edges-in-ubuntu-14-04-ubuntu-13-10-and-earlier-had-a-opti The workaround there is to use ccsm to set Edge Stop Velocity to 0 -- it actually won't set it less than 1, but it works well enough. Still unclear, though, why this has re-surfaced after 7 years, and why turning off sticky edges doesn't do this. ** Description changed: Just upgraded to this: ` DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.3 LTS" ` I've turned off sticky edges but they're still sticky--sometimes! - What's weird about this is that it's only a problem going from the primary (lower) monitor to the secondary (higher). I have them set in an 'above and below' configuration, not horizontal. + What's weird about this is that it's only a problem going from the primary (lower) monitor to the secondary (higher). I have them set in an 'above and below' configuration, not horizontal. Going from the lower monitor to the higher one is really hard. I do not know exactly what package governs this but it wasn't a problem in any previous release since 12.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940761 Title: multi-monitor edges still sticky with Sticky Edges turned off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1940761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940793] Re: Desktop shortcuts disabled after upgrade to 20.04.3 now open in text editor
Hmm I don't seem to be able to close it. Someone else will have to. Still doesn't explain why some shortcuts kept working and others didn't, but there you go. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940793 Title: Desktop shortcuts disabled after upgrade to 20.04.3 now open in text editor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1940793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940793] Re: Desktop shortcuts disabled after upgrade to 20.04.3 now open in text editor
I am closing the bug after finding https://askubuntu.com/questions/1197990/how-to-add-shortcut-starter-to- file-program-or-folder-in-the-desktop-or-menu This is a feasible though not perfect workaround. It seems desktop shortcuts are more or less deprecated in the old form. Procedure: sudo desktop-file-install [some .desktop file which worked before] install and run alacarte, and create a new item. Provide the path used in the .desktop file as is. The item will now appear in Dash with its icon (though not anywhere else) and run. This will have to do by the look of it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940793 Title: Desktop shortcuts disabled after upgrade to 20.04.3 now open in text editor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1940793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940793] Re: Desktop shortcuts disabled after upgrade to 20.04.3 now open in text editor
Additional information. lsb_release -a: No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal screenfetch -n: cmeo@rodan OS: Ubuntu 20.04 focal Kernel: x86_64 Linux 5.4.0-81-generic Uptime: 28m Packages: 2814 Shell: bash 5.0.17 Resolution: 1920x2160 DE: Unity 7.5.0 WM: Compiz WM Theme: Ambiance GTK Theme: Ambiance [GTK2/3] Icon Theme: ubuntu-mono-dark Font: Ubuntu 11 Disk: 136G / 455G (32%) CPU: Intel Core i7-6500U @ 4x 3.1GHz [51.0°C] GPU: Mesa Intel(R) HD Graphics 520 (SKL GT2) RAM: 3545MiB / 15480MiB Digging into this further, I found that there are .desktop files that are working and some that are not. The .desktop files which don't work were created by playonlinux. Here is an example: [Desktop Entry] Encoding=UTF-8 Name=WarInTheEast Comment=PlayOnLinux Type=Application Exec=/usr/share/playonlinux/playonlinux --run "WarInTheEast" %F Icon=/home/cmeo/.PlayOnLinux//icones/full_size/WarInTheEast Name[fr_FR]=WarInTheEast StartupWMClass=WarInTheEast.exe Categories= X-Desktop-File-Install-Version=0.24 And here is one that does work: [Desktop Entry] Type=Application Name=Arduino IDE GenericName=Arduino IDE Comment=Open-source electronics prototyping platform Exec="/home/cmeo/arduino-1.8.12/arduino" Icon=arduino-arduinoide Terminal=false Categories=Development;IDE;Electronics; MimeType=text/x-arduino; Keywords=embedded electronics;electronics;avr;microcontroller; StartupWMClass=processing-app-Base -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940793 Title: Desktop shortcuts disabled after upgrade to 20.04.3 now open in text editor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1940793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940793] [NEW] Desktop shortcuts disabled after upgrade to 20.04.3 now open in text editor
Public bug reported: I have recently upgraded from 18.04 LTS and all my desktop shortcuts are disabled and open in text editor, they do not run the applications. There does not seem to be any clear, documented procedure for fixing this, and I wonder why it has happened in the first place. ** Affects: unity (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/1940793 Title: Desktop shortcuts disabled after upgrade to 20.04.3 now open in text editor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1940793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940761] [NEW] multi-monitor edges still sticky with Sticky Edges turned off
Public bug reported: Just upgraded to this: ` DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.3 LTS" ` I've turned off sticky edges but they're still sticky--sometimes! What's weird about this is that it's only a problem going from the primary (lower) monitor to the secondary (higher). I have them set in an 'above and below' configuration, not horizontal. Going from the lower monitor to the higher one is really hard. I do not know exactly what package governs this but it wasn't a problem in any previous release since 12.04 ** Affects: unity (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/1940761 Title: multi-monitor edges still sticky with Sticky Edges turned off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1940761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880336] Re: Dash search doesn't find anything
I was also affected by this. rm -rf ~/.config/compiz-1 fixed it. Now dash is working as expected. compiz-1 was re-created. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880336 Title: Dash search doesn't find anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1880336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939177] Re: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken
I've also seen this. I wondered if the problem is that the libraries and utilities haven't been updated. I doubt that it's intended for a version 0.8.3 ZFS send and receive to run on a ZFS 2.0.2. kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939177 Title: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938703] [NEW] 5.11 HWE on 20.04 needs new ZFS utils
Public bug reported: The 5.11 HWE for 20.04 has version 2.02 of ZFS, but it doesn't update zfsutils. I found that a zfs send | receive pipe gives an error message, though it seems to work. I don't know for sure that this is due to the version mismatch, but it seems dangerous to use 0.8.3 utilities with 2.0.2 kernel module. I recommend making the 2.0.2 zfsutils available, and possibly installing them by default when the kernel is upgraded. ** Affects: zfsutils (Ubuntu) Importance: Undecided Status: New ** Also affects: zfsutils (Ubuntu) Importance: Undecided Status: New ** No longer affects: nfs-utils (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938703 Title: 5.11 HWE on 20.04 needs new ZFS utils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfsutils/+bug/1938703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932365] [NEW] installer crashed upon install. Using Onn USB 2.0 16gb.
Public bug reported: Ubuntu 18.04.05 LTS AMD64 was what I was trying to install. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.15 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CasperVersion: 1.394.3 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 17 16:39:34 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932365 Title: installer crashed upon install. Using Onn USB 2.0 16gb. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1932365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928377] [NEW] Dist-upgrade failed: 'The package 'ubuntustudio-desktop-core' is marked for removal but it is in the removal blacklist.'
Public bug reported: I can't upgrade. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.15 ProcVersionSignature: Ubuntu 5.8.0-53.60-lowlatency 5.8.18 Uname: Linux 5.8.0-53-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu50.6 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: GNOME Date: Thu May 13 20:10:20 2021 InstallationDate: Installed on 2018-05-28 (1081 days ago) InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to groovy on 2021-05-13 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928377 Title: Dist-upgrade failed: 'The package 'ubuntustudio-desktop-core' is marked for removal but it is in the removal blacklist.' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1928377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918312] Re: group changes don't show up in kerberizedd mounts
Id be happy to help make changes to the relevant tools so I don't need the hacks in that repository if any maintainers would be interested. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918312 Title: group changes don't show up in kerberizedd mounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1918312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918312] Re: group changes don't show up in kerberizedd mounts
I'm well aware of the problem. I see lots of reports that produce discussions that wander off with nothing done, even though there's an actual fix in the thread. I run a moderately large site that uses Kerberos extensively, and kerberoized NFS. I have a whole github repository full of workarounds for problems I can't get fixed. Perhaps this one could be different. https://github.com/clhedrick/kerberos -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918312 Title: group changes don't show up in kerberizedd mounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1918312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920047] [NEW] sanlock global lock creation fail
Public bug reported: Hello, Running Ubuntu server 20.04, I cannot create a shared VG using sanlock : # vgcreate --shared foo /dev/mapper/vol Enabling sanlock global lock Skipping global lock: lockspace not found or started Logical volume "lvmlock" created. VG foo init failed: -28 Failed to initialize lock args for lock type sanlock Volume group "foo" successfully removed Messages in /var/log/syslog lvmlockd[446807]: 1616089866 WARNING: mixed block sizes physical 4096 logical 512 (using 4096) for /dev/mapper/foo-lvmlock lvmlockd[446807]: 1616089866 S lvm_foo init_vg_san write_resource gl error -28 /dev/mapper/foo-lvmlock # lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 # dpkg -l | grep lvm ii liblvm2cmd2.03:amd64 2.03.07-1ubuntu1 amd64LVM2 command library ii lvm2 2.03.07-1ubuntu1 amd64Linux Logical Volume Manager ii lvm2-lockd 2.03.07-1ubuntu1 amd64LVM locking daemon A similar bug report from RHEL8 : https://bugzilla.redhat.com/show_bug.cgi?id=1833837 Bug has been fixed upstream : https://sourceware.org/git/?p=lvm2.git;a=commit;h=2d1fe38d84d499011d13ae1ea11535398528fc87 It seems to be included in version 2.03.10 : https://sourceware.org/git/?p=lvm2.git;a=shortlog;h=refs/tags/v2_03_10 How can we get this patch included in Ubuntu 20.04 ? King Regards, Charles ** Affects: lvm2 (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/1920047 Title: sanlock global lock creation fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1920047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918313] [NEW] code in rpc.svcgssd treats date as signed 32-bit
Public bug reported: Upstream patch eb3a145789b9eedd39b56e1d76f412435abaa747 adds code to rpc.svcgssd to set an expiration date for nfs contexts. (It doesn't work, but that's the subject of a different bug.) That code treats the date is int32. It is sent into the kernel using code that ends up as a printf %d. In 2038 the date will go negative. Because the kernel uses 64-bit dates I believe that will produce the wrong result. The code should use data_t, not int32_t. This is complicated by the fact that it gets the date from a Kerberos ticket. Kerberos declares date as int32. For historical reaosns, they have decided to retain it as int32, but whenever there's a comparison or arithemtic that would break, they cast it (date_t)(u_int32_t). I believe the code in svcgssdd should do the same. All variables should be date_t. Anything retrieved from a Kerberos ticket should be cast (date_t)(u_int32_t). THis is actually a problem upstream. But it's not clear that upstream has any reason to fix it. Redhat is no longer using rpc.svcgssd. They're using gssproxy to handle the upcall from the kernel. So it's not clear that there's any significant use of svcgssd other than Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nfs-common 1:1.3.4-2.5ubuntu3.3 [modified: usr/sbin/rpc.svcgssd] ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Mar 9 12:46:12 2021 InstallationDate: Installed on 2020-03-25 (348 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=vt100 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/tcsh SourcePackage: nfs-utils UpgradeStatus: Upgraded to focal on 2020-12-21 (78 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-08-10T17:26:17.512725 mtime.conffile..etc.default.nfs-common: 2020-04-16T16:03:31.356462 ** Affects: nfs-utils (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/1918313 Title: code in rpc.svcgssd treats date as signed 32-bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1918313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917429] [NEW] grug-efi-amd64-signed failed to install to target
Public bug reported: Try to install ubuntu 18 into my old window7 PC. As I don't need the Window 7 anymore. I decided to erase all old data and system. Then I get the message " grub-efi-amd64-signed" fail to install to target. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 2 00:46:54 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: LANGUAGE=en_CA.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.12 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917429 Title: grug-efi-amd64-signed failed to install to target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1917429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916803] [NEW] A fatal error has been detected by the Java Runtime Environment:
Public bug reported: A fatal error has been detected by the Java Runtime Environment: 3 # 4 # SIGSEGV (0xb) at pc=0x007d74cf8e30, pid=6492, tid=6493 5 # 6 # JRE version: OpenJDK Runtime Environment (11.0.7+10) (build 11.0.7+10-post-Ubuntu-3ubuntu1) 7 # Java VM: OpenJDK 64-Bit Server VM (11.0.7+10-post-Ubuntu-3ubuntu1, mixed mode, tiered, compressed oops, g1 gc, linux-aarch64) Description:Ubuntu 20.04.2 LTS Release:20.04 8 # Problematic frame: 9 # C [libgobject-2.0.so.0+0x3ce30] g_type_check_instance_is_fundamentally_a+0x38 ** Affects: openjdk-lts (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/1916803 Title: A fatal error has been detected by the Java Runtime Environment: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1916803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8
I have also had the boot problem disappear, return, and disappear again. On 1/22/21 11:12 AM, Wolf Pichler wrote: > I have these installed: > > dpkg -l | grep "linux\-[a-z]*\-" > > rc linux-modules-extra-5.4.0-42-generic 5.4.0-42.46 > ii linux-modules-extra-5.4.0-58-generic 5.4.0-58.64 > ii linux-modules-extra-5.8.0-36-generic 5.8.0-36.40~20.04.1 > ii linux-modules-extra-5.8.0-38-generic 5.8.0-38.43~20.04.1 > > I tried as Charles Green said: Switching to tty2 and then back to tty1 causes > the boot to complete. > (Ctrl+Alt+F2, Ctrl+Alt+F1) > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8
The ctrl+alt+f2 - this was a fresh install on a system76 machine, running the integrated graphics. I have since loaded the NVidia drivers and my some miracle, I no longer need this work around. The ttys run from 1 to 7, I think, but the keyboard shortcuts to activate them are always ctrl+alt+f(num) On 1/20/21 12:18 PM, Ben Hoyt wrote: > Charles, very interesting. Though I wonder if yours is a different > problem, partly because it's not in tty mode at all (for me it's in a > graphical mode, sometimes with the Dell logo up). I can't seem to switch > to tty2 using Alt-F2 or Ctrl-Alt-F2 -- what are the exact keys you're > using? > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8
I've got the same issue on a system76 gazelle - I just reinstalled 20.04 hoping that this would fix the issue, but the 5.8.0-38 kernel does not complete the boot cycle by itself. I have found that switching to tty2 and then back to tty1 causes the boot to complete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910875] Re: Broadcom wireless driver failed to install with code 10 on focal 20.04
@jsarka, Thanks for those clear instructions! As it turns out I already figured out (I hope) how to revert to kernel 5.4. That has brought back my wifi. If other things go bonkers, I'll get 5.8 back and follow your steps. The bump to 5.8 broke several things on my system, which is why I first tried downgrading kernels. I deliberately picked an LTS, so I'm very surprised that I got a kernel bump that skips three point releases without any warning. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910875 Title: Broadcom wireless driver failed to install with code 10 on focal 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910876] [NEW] wifi no longer recognized
Public bug reported: Within the last couple of hours there was a batch of system updates presented to me by Discover in KDE. I installed them and restarted like it said to. Upon restart, there is no wifi. If I do `nmcli dev`, I no longer see my wifi device listed at all. It used to be listed as "wlp2s0". Rebooting, or shutting down and restarting cold, didn't help. This is on Ubuntu 20.04, kernel version 5.8.0-36-generic (according to "System Information" in KDE's "System Settings"). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-36-generic 5.8.0-36.40~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Jan 9 18:17:37 2021 InstallationDate: Installed on 2020-08-19 (143 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: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.8 (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/1910876 Title: wifi no longer recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1910876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910875] Re: Broadcom wireless driver failed to install with code 10 on focal 20.04
I'm new to Linux, so bear with me, but...Within the last hour or so I installed a bunch of system updates in KDE Discover, and suddenly wifi stopped working after the enforced restart. By "stopped working", I mean I have no internet connection via wifi and `nmcli dev` no longer lists my wireless device "wlp2so" *at all*. I'm on an Apple MacBookPro9,2 running 20.04 with KDE. "Driver Manger" tells me I'm using "Broadcom 802.11 Linux STA wireless driver source from bcmwl-kernel-source (proprietary)", for the BCM4331 device. I tried clicking "Do not use the device" and then re-enabling it but I got some cryptic error. Upon re-opening Driver Manager it again says I'm using the proprietary driver. I hope this can be quickly fixed, since this machine is now internet- free except for the occasional times I can plug into ethernet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910875 Title: Broadcom wireless driver failed to install with code 10 on focal 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907988] [NEW] package mysql-server-8.0 8.0.22-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
Public bug reported: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.22-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Dec 13 22:48:03 2020 ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-12-12 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLVarLibDirListing: ['sys', '#innodb_temp', 'ibdata1', 'binlog.02', 'mysql.ibd', 'public_key.pem', 'performance_schema', 'client-cert.pem', 'debian-5.7.flag', 'client-key.pem', 'binlog.index', '#ib_16384_0.dblwr', 'undo_002', 'ib_logfile1', 'server-key.pem', 'ca-key.pem', 'mysql', 'binlog.01', 'server-cert.pem', 'ib_buffer_pool', 'auto.cnf', '#ib_16384_1.dblwr', 'undo_001', 'ib_logfile0', 'private_key.pem', 'ca.pem'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=f2180afc-c4d8-4e78-bba0-0be462be5f68 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.5, python-is-python3, 3.8.2-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.22-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-8.0 (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/1907988 Title: package mysql-server-8.0 8.0.22-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1907988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903323] [NEW] trying to get apps to show on gnome store returns error code
Public bug reported: when I try the sudo apt-get update command to fix apps not showing in the gnome-software center it produces the following error E: The repository 'http://ppa.launchpad.net/ehoover/compholio/ubuntu hirsute Release' does not have a Release file. ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903323 Title: trying to get apps to show on gnome store returns error code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1903323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896543] [NEW] installer crash
Public bug reported: I'm trying to install Ubunto 20.04 again because I couldn't get the sound to work, though it does downstairs on another computer with essentially the same specs. I've installed it at least 3 times and always seem to have trouble with the boot loader. I'm trying for a triple boot system. Windows10 on a HDD and BionicPup and Ubuntu on an SSD. I had it working except for the sound. It seems to be making more partitions each time I install, because it mentioned sdd5 and 6, then the next attempt it mentioned sdd6 and 7. I have it erase and reinstall, so I would have thought it would just use the same partition designations, but it doesn't. I'm pretty new to Linux, and am not super skilled in computers, but I'm able to play around with things, look online, and eventually figure things out. IF I can get Ubuntu to install again I'll use Rescatux to fix the bootloader issue. Last time it listed the 3 OSs, but only Windows and Pup worked from the choices and IU had to use boot options and go to the ssd to boot Ubuntu. I hope I can do that again. IDK why the sound didn't work up here, but the one downstairs does. I tried EVERYTHING I could find to fix it. I'm on an old Dell PrecisionT7500, it's an old enough system it should detect things and just work;perhaps another bug. THANK YOU for the work you do. I LOVE Linux when it works, but have to keep Windows for when things won't work on Linux. I hope this information is helpful. Charles ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 21 16:01:32 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896543 Title: installer crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1896543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889021] [NEW] package python3-software-properties 0.98.9 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
Public bug reported: Check if you are using third party repositories. If so disable them, since they are a common source of problems. Furthermore run the following command in a Terminal: apt-get install -f Transaction failed: The package system is broken The following packages have unmet dependencies: software-properties-gtk: Depends: gir1.2-goa-1.0 (>= 3.27.92-1ubuntu1) but 3.36.0-1ubuntu1 is installed Depends: gir1.2-snapd-1 (>= 1.42) but 1.57-0ubuntu3 is installed Depends: python3-software-properties (= 0.98.9.1) but 0.98.9 is installed Depends: ubuntu-drivers-common (>= 1:0.2.75) but 1:0.8.1.1 is installed Depends: python3:any but it is a virtual package ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python3-software-properties 0.98.9 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jul 26 21:03:14 2020 ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2020-07-27 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: software-properties Title: package python3-software-properties 0.98.9 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (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/1889021 Title: package python3-software-properties 0.98.9 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1889021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888881] [NEW] calculating fails when upgrading from 28.04 to 20.04
Public bug reported: Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Jul 24 17:09:29 2020 InstallationDate: Installed on 2020-07-09 (14 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-07-24 (0 days ago) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2020-07-24T15:50:47.394303 ** 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/181 Title: calculating fails when upgrading from 28.04 to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883886] Re: Print dialogue's height in Libreoffice Writer is too high to see and click buttons.
** Changed in: libreoffice (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883886 Title: Print dialogue's height in Libreoffice Writer is too high to see and click buttons. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1883886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835024] Re: Links triggered within most snap apps open in a separate browser session
I just wanted to comment that this is more than just Slack "owning" apps opened from inside Slack. It also messes up the audio/video setup inside the "owned" app. For example, if I launch snap Slack before Chrome and try to join a Zoom call from Slack, then my A/V options are limited only to the built-in devices in my laptop. This makes Zoom unusable for me, so I have to make sure I always launch Chrome before Slack. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835024 Title: Links triggered within most snap apps open in a separate browser session To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1835024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879164] Re: Copy/cut/paste is broken in wine applications
This problem is bad news for users of Office 2010 running under Wine on Ubuntu 20.04 The latest stable version of Wine seems to fix this issue: fonts-wine5.0-3ubuntu1 libkwineffects12 4:5.18.5-0ubuntu0.1 libwine:i386 5.0-3ubuntu1 wine-stable 5.0.1~focal wine-stable-amd64 5.0.1~focal wine-stable-i386:i386 5.0.1~focal wine32:i386 5.0-3ubuntu1 winehq-stable 5.0.1~focal Here are the instructions from https://wiki.winehq.org/Ubuntu to install the latest version: If your system is 64 bit, enable 32 bit architecture (if you haven't already): sudo dpkg --add-architecture i386 Download and add the repository key: wget -O - https://dl.winehq.org/wine-builds/winehq.key | sudo apt-key add - Add the repository: For Ubuntu 20.04: sudo add-apt-repository 'deb https://dl.winehq.org/wine-builds/ubuntu/focal main' Update packages & then install: sudo apt update sudo apt install --install-recommends winehq-stable -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879164 Title: Copy/cut/paste is broken in wine applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1879164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884536] Re: Multiple-monitor Set Up Makes Mouse-pointer Jump About in 20.04
** Package changed: ubuntu => gpm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884536 Title: Multiple-monitor Set Up Makes Mouse-pointer Jump About in 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpm/+bug/1884536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883886] Re: Print dialogue's height in Libreoffice Writer is too high to see and click buttons.
** Tags added: lubuntu ** Tags added: libreoffice libreoffice-writer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883886 Title: Print dialogue's height in Libreoffice Writer is too high to see and click buttons. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1883886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884584] [NEW] Envy 5030 Printer unable to be setup via hplip Lubuntu 20.04
Public bug reported: Information via $ lsb_release -rd: Description:Ubuntu 20.04 LTS Release:20.04 Information via $ apt-cache policy hplip hplip: Installed: 3.20.3+dfsg0-2 Candidate: 3.20.3+dfsg0-2 Version table: *** 3.20.3+dfsg0-2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Relevant hplip package information: $ dpkg -l hplip* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-==-==-- ii hplip 3.20.3+dfsg0-2 amd64HP Linux Printing and Imaging System (HPLIP) un hplip-cups (no description available) ii hplip-data 3.20.3+dfsg0-2 all HP Linux Printing and Imaging - data files un hplip-doc (no description available) ii hplip-gui 3.20.3+dfsg0-2 all HP Linux Printing and Imaging - GUI utilities (Qt-based) Hello, newbie here, I am unable to setup and use my HP Envy 5030 printer on my Lubuntu 20.04 system. Steps to reproduce the problem: I am trying to setup my printer via wifi. 1) I run hp-setup from the terminal. 2) I select the 'Wireless/802.11' option and click next. 3) I plug my printer in via usb cable and press next. 4) My printer is recognized and I press next. 5) An error dialog pops up saying "An I/O error occurred. Please check the USB connection to your printer and try again. (Device I/O error)". Moreover, the terminal displays a 'Channel write error'. (please see the attached screenshot). Please find attached the results of the hp-check.log file; it is worth noting that a warning message is displayed in the file indicating that Ubuntu 20.04 is not supported. Regarding the Missing Required Dependencies via the hp-check.log file: libcups2 - is installed. python3-pyqt4 - has been replaced with python3-pyqt5 gtk2-engines-pixbuf - is installed. I am able to set up the printer with hp-setup when selecting the USB option. I am able to print but not scan. I have previously installed the hplip package via the automatic installer on the HP website (https://developers.hp.com/hp-linux-imaging- and-printing), but this didn't work either. Important to note that the automatic installer does not support Ubuntu 20.04, so no surprise there. Thank you in advance, Owen ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: hplip 3.20.3+dfsg0-2 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Mon Jun 22 19:22:07 2020 InstallationDate: Installed on 2020-06-05 (16 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for ENVY_5000_series_TH79S4C0PZ_: implicitclass://ENVY_5000_series_TH79S4C0PZ_/ MachineType: LENOVO 81J1 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/ENVY_5000_series_TH79S4C0PZ_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/ENVY_5000_series_TH79S4C0PZ_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=53a299e0-a9e5-4e56-b902-0f79b0931a13 ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN23WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32802WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad S130-11IGM dmi.modalias: dmi:bvnLENOVO:bvr9HCN23WW:bd04/18/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM: dmi.product.family: ideapad S130-11IGM dmi.product.name: 81J1 dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM dmi.product.version: Lenovo ideapad S130-11IGM dmi.sys.vendor: LENOVO ** Affects: hplip (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal hplip lubuntu ** Attachment added: "Contains a screenshot of the issue as well as the hp-check.log file" https://bugs.launchpad.net/bugs/1884584/+attachment/5386154/+files/hplip_bug.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884584 Title: Envy 5030 Printer unable to be setup via hplip Lubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1884584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
[Bug 1884536] [NEW] Multiple-monitor Set Up Makes Mouse-pointer Jump About in 20.04
Public bug reported: I have relatively recently loaded Ubuntu 20.04 to dual-boot on a Packard Bell with Windows 10 Home 64-bit already installed. The mouse-pointer moves and clicks perfectly when the PC has a single-monitor. However, for work as a developer, I should like to use a dual-monitor setup. The problem I have is, if I plug in to the PC tower a second monitor and follow the steps to Connect Another Monitor To My Computer (https://help.ubuntu.com/stable/ubuntu-help/display-dual-monitors.html), and after I confirm "join Display", the mouse-pointer jumps about and a second stationary mouse-pointer appears in the bottom right of my primary screen. This behaviour stops immediately I confirm "Single Display", but now the second screen is now turned blank. $ xinput ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ USB Wired Keyboard Consumer Control id=12 [slave pointer (2)] ⎜ ↳ PixArt USB Optical Mouse id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ Sleep Button id=9[slave keyboard (3)] ↳ USB Wired Keyboardid=10 [slave keyboard (3)] ↳ USB Wired Keyboard System Control id=11 [slave keyboard (3)] ↳ USB Wired Keyboard Consumer Control id=14 [slave keyboard (3)] $ sudo dmidecode -t 1 # dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Packard Bell Product Name: iMedia S2984 Version: Serial Number: DTU96EK00360103D0F3000 UUID: 84edd4a2-b457-11e5-9b1f-98eecb2ca5dd Wake-up Type: Power Switch SKU Number: Family: Packard Bell Desktop $ lsb_release -a; uname -a; lsusb No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal Linux charlesb2t-iMedia-S2984 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0153 Realtek Semiconductor Corp. 3-in-1 (SD/SDHC/SDXC) Card Reader Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 002: ID 0461:4e6f Primax Electronics, Ltd Acer Wired Keyboard Model KBAY211 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I am reporting this as a bug because I am unable to fix it and I have asked around, but no joy. I do need a dual-monitor set p for work. Currently, I can use Windows10 with dual-monitors, on the same machine, without a glitch. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884536 Title: Multiple-monitor Set Up Makes Mouse-pointer Jump About in 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1884536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883886] [NEW] Print dialogue's height in Libreoffice Writer is too high to see and click buttons.
Public bug reported: Hello, I have the bug that is denoted here https://ask.libreoffice.org/en/question/240651/print-dialogue-too-large- to-select-ok-to-print/ and here https://bugs.documentfoundation.org/show_bug.cgi?id=127782#c67. Essentially, the libreoffice writer print's dialog box is too high for me to view and press the buttons with the mouse. A workaround is to just press ENTER to print. Please see the following screenshot for an example: https://snipboard.io/vc1X0f.jpg My information is as follows: Results of lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 Results of apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:6.4.3-0ubuntu0.20.04.1 Candidate: 1:6.4.3-0ubuntu0.20.04.1 Version table: *** 1:6.4.3-0ubuntu0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:6.4.2-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Just FYI in case it is necessary: I am using Lubuntu 20.04 LTS with LXQt. Best regards, Owen Charles ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-writer 1:6.4.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Wed Jun 17 12:47:56 2020 InstallationDate: Installed on 2020-06-05 (11 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883886 Title: Print dialogue's height in Libreoffice Writer is too high to see and click buttons. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1883886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880775] [NEW] HP Envy 4524 All In One - Device communication error - code 5012;
Public bug reported: Situation: Ubuntu 20.04 LTS after fresh install, NOT upgrade on desktop (had 16.04 LTS before). Printer was attached during fresh install of 20.04 LTS and internet connection, third party downloads ticked. Bug description: USB connected HP Envy 4524 All In One is recognized multiple times as printer but does not print, scans occasionally but unreliable in getting recognized by 20.04 LTS. Additional Information: HP Envy 4524 All In One works flawless with Ubuntu 18.04 LTS on Laptop. Worked flawless with Ubuntu 16.04 LTS on the desktop used above. Steps taken so far: De-installed/purged hplip 3.20.3 as sudo hp-check -i showed multiple errors and missing dependencies. Installed hplip 3.20.5 from the HPLIP site and ran the script which resulted in compiling and installing the printer with nil errors running sudo hp-check -i. However, after reboot Device communication error - code 5012 re-occured (current hp-check log attached). Log ___ administrator@office-server:~$ sudo hp-check -i [sudo] password for administrator: /usr/bin/hp-check:685: SyntaxWarning: "is not" with a literal. Did you mean "!="? if 'getfacl' not in g and '' is not g and 'file' not in g: Saving output in log file: /home/administrator/hp-check.log HP Linux Imaging and Printing System (ver. 3.20.5) Dependency/Version Check Utility ver. 15.1 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Note: hp-check can be run in three modes: 1. Compile-time check mode (-c or --compile): Use this mode before compiling the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies are installed to successfully compile HPLIP. 2. Run-time check mode (-r or --run): Use this mode to determine if a distro supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball has the proper dependencies installed to successfully run. 3. Both compile- and run-time check mode (-b or --both) (Default): This mode will check both of the above cases (both compile- and run-time dependencies). Check types: a. EXTERNALDEP - External Dependencies b. GENERALDEP - General Dependencies (required both at compile and run time) c. COMPILEDEP - Compile time Dependencies d. [All are run-time checks] PYEXT SCANCONF QUEUES PERMISSION Status Types: OK MISSING - Missing Dependency or Permission or Plug-in INCOMPAT - Incompatible dependency-version or Plugin-version |Gtk-Message: 09:51:18.656: Failed to load module "canberra-gtk-module" --- | SYSTEM INFO | --- Kernel: 5.4.0-31-generic #35-Ubuntu SMP Thu May 7 20:20:34 UTC 2020 GNU/Linux Host: office-server Proc: 5.4.0-31-generic #35-Ubuntu SMP Thu May 7 20:20:34 UTC 2020 GNU/Linux Distribution: 12 20.04 Bitness: 64 bit --- | HPLIP CONFIGURATION | --- HPLIP-Version: HPLIP 3.20.5 HPLIP-Home: /usr/share/hplip HPLIP-Installation: Auto installation is supported for ubuntu distro 20.04 version Current contents of '/etc/hp/hplip.conf' file: # hplip.conf. Generated from hplip.conf.in by configure. [hplip] version=3.20.5 [dirs] home=/usr/share/hplip run=/var/run ppd=/usr/share/ppd/HP ppdbase=/usr/share/ppd doc=/usr/share/doc/hplip-3.20.5 html=/usr/share/doc/hplip-3.20.5 icon=/usr/share/applications cupsbackend=/usr/lib/cups/backend cupsfilter=/usr/lib/cups/filter drv=/usr/share/cups/drv/hp bin=/usr/bin apparmor=/etc/apparmor.d # Following values are determined at configure time and cannot be changed. [configure]
[Bug 1869522] Re: Simple Scan doesn't work
Thanks for the response. "Bug" was resolved by Bartosz, reference: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1869524 now when I run $ which simple-scan the result is: /usr/bin/simple-scan as expected. When I run $ ldd -r /usr/bin/simple-scan the result is: linux-vdso.so.1 (0x7ffe617db000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7febc9a62000) libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x7febc974b000) libgtk-3.so.0 => /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 (0x7febc8e43000) libgdk-3.so.0 => /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 (0x7febc8b4d000) libcairo.so.2 => /usr/lib/x86_64-linux-gnu/libcairo.so.2 (0x7febc883) libgdk_pixbuf-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7febc860c000) libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 (0x7febc826d000) libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x7febc8019000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7febc7dfc000) libgusb.so.2 => /usr/lib/x86_64-linux-gnu/libgusb.so.2 (0x7febc7bee000) libsane.so.1 => /usr/lib/x86_64-linux-gnu/libsane.so.1 (0x7febc79bf000) libcolord.so.2 => /usr/lib/x86_64-linux-gnu/libcolord.so.2 (0x7febc779f000) libpackagekit-glib2.so.18 => /usr/lib/x86_64-linux-gnu/libpackagekit-glib2.so.18 (0x7febc7543000) libwebp.so.6 => /usr/lib/x86_64-linux-gnu/libwebp.so.6 (0x7febc72da000) libwebpmux.so.3 => /usr/lib/x86_64-linux-gnu/libwebpmux.so.3 (0x7febc70d) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7febc6cdf000) /lib64/ld-linux-x86-64.so.2 (0x7febca06b000) libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7febc6a6d000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7febc684e000) libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (0x7febc664a000) libpangocairo-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 (0x7febc643d000) libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x7febc6105000) libXi.so.6 => /usr/lib/x86_64-linux-gnu/libXi.so.6 (0x7febc5ef5000) libXfixes.so.3 => /usr/lib/x86_64-linux-gnu/libXfixes.so.3 (0x7febc5cef000) libcairo-gobject.so.2 => /usr/lib/x86_64-linux-gnu/libcairo-gobject.so.2 (0x7febc5ae6000) libatk-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libatk-1.0.so.0 (0x7febc58c) libatk-bridge-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0 (0x7febc568f000) libepoxy.so.0 => /usr/lib/x86_64-linux-gnu/libepoxy.so.0 (0x7febc538e000) libpangoft2-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0 (0x7febc5178000) libpango-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 (0x7febc4f2b000) libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x7febc4ce6000) libXinerama.so.1 => /usr/lib/x86_64-linux-gnu/libXinerama.so.1 (0x7febc4ae3000) libXrandr.so.2 => /usr/lib/x86_64-linux-gnu/libXrandr.so.2 (0x7febc48d8000) libXcursor.so.1 => /usr/lib/x86_64-linux-gnu/libXcursor.so.1 (0x7febc46ce000) libXcomposite.so.1 => /usr/lib/x86_64-linux-gnu/libXcomposite.so.1 (0x7febc44cb000) libXdamage.so.1 => /usr/lib/x86_64-linux-gnu/libXdamage.so.1 (0x7febc42c8000) libxkbcommon.so.0 => /usr/lib/x86_64-linux-gnu/libxkbcommon.so.0 (0x7febc4089000) libwayland-cursor.so.0 => /usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0 (0x7febc3e81000) libwayland-egl.so.1 => /usr/lib/x86_64-linux-gnu/libwayland-egl.so.1 (0x7febc3c7f000) libwayland-client.so.0 => /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 (0x7febc3a7) libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x7febc385e000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7febc3656000) libpixman-1.so.0 => /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 (0x7febc33b1000) libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 (0x7febc30fd000) libpng16.so.16 => /usr/lib/x86_64-linux-gnu/libpng16.so.16 (0x7febc2ecb000) libxcb-shm.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-shm.so.0 (0x7febc2cc8000) libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x7febc2aa) libxcb-render.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-render.so.0 (0x7febc2893000) libXrender.so.1 => /usr/lib/x86_64-linux-gnu/libXrender.so.1 (0x7febc2689000) libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x7febc2461000) libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x7febc2246000) libmount.so.1 => /lib/x86_64-linux-gnu/libmount.so.1
[Bug 1878617] Re: Apple pages file type should be added to MIME types
Hello, You can add `application/vnd.apple.pages pages` in `/etc/mime.types` on your system, and I will do it in a future update of the `mime-support` package, but it will not effect the output of the `file` command, which uses a different database. You can open a bug on the `file` package to request it, but please have a look if you can at <https://github.com/file/file/tree/master/magic> before: as you will see, unless you can provide a “magic number” for that format (a proprietary format from a proprietary software, if I may comment), it may not be possible to detect it. You can also have a look at the `shared-mime-info` package for another way to associate the `.pages` file suffix to the `application/vnd.apple.pages` media type. Have a nice day, Charles Plessy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878617 Title: Apple pages file type should be added to MIME types To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1878617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876046] Re: [XPS L501X, Realtek ALC665, Speaker, Internal]
I have a Dell XPS L501X with exactly the same problem. The fix above: > volume control -> configuration to Analog Stereo Duplex (unplugged) I the only thing that has worked for me. I've tried multiple other suggestions on other sites, include renaming .config/pulse folder then reboot, force-reload of alsa, removing the pulse-audio and alsa-base packages from the system, and reinstalling them, and reviewing all settings in alsa mixer. Ubuntu works perfectly on this laptop. I had 19.04 previously, and sound worked fine. An upgrade to 20.04 didn't work as selecting the nVidia video driver nvidia-driver-390 would not let the OS boot into the GUI. What is strange is a complete wipe and reinstall of 20.04 from scratch worked fine, and that video driver was selected automatically. I'm so glad I found this post, as I now have sound again. For now I'm content changing the setting by hand after a reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876046 Title: [XPS L501X, Realtek ALC665, Speaker, Internal] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 663962] Re: linthesia crashes with GdkGLExt-WARNING **: cannot load PangoFont
Hi, we made 2 patches to fix this issue. original : https://github.com/linthesia/linthesia/pull/37 May I suggest you use this version : https://github.com/mans17/linthesia -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/663962 Title: linthesia crashes with GdkGLExt-WARNING **: cannot load PangoFont To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linthesia/+bug/663962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869524] Re: Simple Scan doesn't load
That did it! "Bug" fixed. :) Thanks Bartosz! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869524 Title: Simple Scan doesn't load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1869524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
