[Bug 2067658] [NEW] Driver issue for Intel Alder Lake-P GT2 [Iris Xe Graphics] appears in Noble Numbat
Public bug reported: After upgrading to 24.04 LTS (Noble Numbat) from lubuntu 23.10 the system no longer boots except in safe mode. A fresh install of Noble Numbat was done, but this did not resolve the problem. In the grub file /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT='quiet splash' was changed to GRUB_CMDLINE_LINUX_DEFAULT='quiet splash nomodeset ' and now the system boots. $ sudo sudo lshw -c video *-display description: VGA compatible controller product: Alder Lake-P GT2 [Iris Xe Graphics] vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 logical name: /dev/fb0 version: 0c width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list fb configuration: depth=32 latency=0 mode=1920x1200 visual=truecolor xres=1920 yres=1200 resources: iomemory:600-5ff iomemory:400-3ff memory:603c00-603cff memory:40-400fff ioport:2000(size=64) memory:c-d memory:401000-4016ff memory:402000-40 *-graphics product: simpledrmdrmfb physical id: 2 logical name: /dev/fb0 capabilities: fb configuration: depth=32 resolution=1920,1200 $ inxi -G Graphics: Device-1: Intel Alder Lake-P GT2 [Iris Xe Graphics] driver: N/A Device-2: Luxvisions Innotech Integrated Camera driver: uvcvideo type: USB Display: x11 server: X.Org v: 21.1.11 driver: X: loaded: modesetting,vesa unloaded: fbdev dri: swrast gpu: N/A resolution: 1920x1200~60Hz API: EGL v: 1.5 drivers: kms_swrast,swrast platforms: gbm,x11,surfaceless,device API: OpenGL v: 4.5 vendor: mesa v: 24.0.5-1ubuntu1 renderer: llvmpipe (LLVM 17.0.6 256 bits) It would appear that the driver support for Alder Lake-P GT2 [Iris Xe Graphics] has changed between lubuntu 23.10 and 24.04 LTS (Noble Numbat). This issue was not observed in lubuntu 23.10. ** Affects: lubuntu-meta (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/2067658 Title: Driver issue for Intel Alder Lake-P GT2 [Iris Xe Graphics] appears in Noble Numbat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/2067658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063271] Re: Illegal opcode in libssl
Thank you for your quick and helpful reply. A few quick checks make it appear that reinstalling libssl as you suggested has completely resolved the problem. Thanks also for your suggestion about checking failing hardware. There seems to be no sign of any errors in my drive, but I'll continue to test the drive and my RAM. Perhaps it was just a stray cosmic ray. Thanks again and best wishes to successful bug smashing! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063271 Title: Illegal opcode in libssl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2063271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063271] Re: Illegal opcode in libssl
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063271 Title: Illegal opcode in libssl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2063271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964697] [NEW] speedtest-cli crash
Public bug reported: When called from crontab, speedtest-cli sometimes crashes. Crashes tend to occur more frequently shortly after a reboot. cat /etc/cron.d/speedtest # UncleT scripts to monitor upstream network SHELL=/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin */15 * * * *root/usr/bin/speedtest-cli 2>&1 See crash dump for details ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: speedtest-cli 2.1.2-2ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckMismatches: ./pool/main/l/linux-hwe-5.11/linux-modules-extra-5.11.0-34-generic_5.11.0-34.36~20.04.1_amd64.deb CasperMD5CheckResult: fail Date: Sun Mar 13 01:13:40 2022 InstallationDate: Installed on 2021-12-29 (73 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210914) PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color PATH=(custom, no user) SourcePackage: speedtest-cli UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.logrotate.d.apport: 2021-12-18T21:15:17 ** Affects: speedtest-cli (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/1964697 Title: speedtest-cli crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speedtest-cli/+bug/1964697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877658] Re: very buggy on download exe with sourceforge
Errors like this are still common during install: Get:1 http://downloads.sourceforge.net/corefonts/andale32.exe [198 kB] Fetched 198 kB in 1s (213 kB/s) Err:1 http://downloads.sourceforge.net/corefonts/arial32.exe Could not resolve 'iweb.dl.sourceforge.net' E: Failed to fetch http://iweb.dl.sourceforge.net/project/corefonts/the fonts/final/arial32.exe Could not resolve 'iweb.dl.sourceforge.net' E: Download Failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877658 Title: very buggy on download exe with sourceforge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msttcorefonts/+bug/1877658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954635] Re: subiquity crashes when attempting advanced network/disk configuration
The major number would suggest that it's a logical volume, but it doesn't seem to correspond to a logical volume, so I'm not sure what it is: # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:00 377.4M 1 loop /media/filesystem loop1 7:10 221.8M 1 loop loop2 7:20 82.1M 1 loop /usr/lib/modules loop3 7:30 61.9M 1 loop /snap/core20/1270 loop4 7:40 42.2M 1 loop /snap/snapd/14066 loop5 7:50 67.2M 1 loop /snap/lxd/21835 loop6 7:60 24.3M 1 loop /snap/subiquity/2974 sda 8:01 119.5G 0 disk ├─sda1 8:11 119.5G 0 part │ └─ventoy253:80 1.2G 1 dm /cdrom └─sda2 8:2132M 0 part sr011:01 1024M 0 rom nvme0n1 259:00 953.9G 0 disk ├─nvme0n1p1 259:40 260M 0 part ├─nvme0n1p2 259:6016M 0 part ├─nvme0n1p3 259:70 952.6G 0 part └─nvme0n1p4 259:80 995M 0 part nvme1n1 259:10 953.9G 0 disk ├─nvme1n1p1 259:20 512M 0 part ├─nvme1n1p2 259:30 1G 0 part └─nvme1n1p3 259:50 952.4G 0 part ├─kangaroovg-rootlv 253:00 5G 0 lvm ├─kangaroovg-usrlv 253:1020G 0 lvm ├─kangaroovg-varlv 253:20 5G 0 lvm ├─kangaroovg-varliblv 253:30 7G 0 lvm ├─kangaroovg-homelv 253:40 100G 0 lvm ├─kangaroovg-srvlv 253:50 5G 0 lvm ├─kangaroovg-usrlocallv 253:60 5G 0 lvm └─kangaroovg-swaplv 253:70 8G 0 lvm # ls -l /dev/dm* brw-rw 1 root disk 253, 0 Dec 16 03:20 /dev/dm-0 brw-rw 1 root disk 253, 1 Dec 16 03:20 /dev/dm-1 brw-rw 1 root disk 253, 2 Dec 16 03:20 /dev/dm-2 brw-rw 1 root disk 253, 3 Dec 16 03:20 /dev/dm-3 brw-rw 1 root disk 253, 4 Dec 16 03:20 /dev/dm-4 brw-rw 1 root disk 253, 5 Dec 16 03:20 /dev/dm-5 brw-rw 1 root disk 253, 6 Dec 16 03:20 /dev/dm-6 brw-rw 1 root disk 253, 7 Dec 16 03:20 /dev/dm-7 brw-rw 1 root disk 253, 8 Dec 16 03:20 /dev/dm-8 /dev/dma_heap: total 0 crw--- 1 root root 249, 0 Dec 16 03:20 system # lvscan ACTIVE'/dev/kangaroovg/rootlv' [5.00 GiB] inherit ACTIVE'/dev/kangaroovg/usrlv' [20.00 GiB] inherit ACTIVE'/dev/kangaroovg/varlv' [5.00 GiB] inherit ACTIVE'/dev/kangaroovg/varliblv' [7.00 GiB] inherit ACTIVE'/dev/kangaroovg/homelv' [100.00 GiB] inherit ACTIVE'/dev/kangaroovg/srvlv' [5.00 GiB] inherit ACTIVE'/dev/kangaroovg/usrlocallv' [5.00 GiB] inherit ACTIVE'/dev/kangaroovg/swaplv' [8.00 GiB] inherit # vgscan Found volume group "kangaroovg" using metadata type lvm2 # ls -l /dev/kangaroovg total 0 lrwxrwxrwx 1 root root 7 Dec 16 08:58 homelv -> ../dm-4 lrwxrwxrwx 1 root root 7 Dec 16 08:58 rootlv -> ../dm-0 lrwxrwxrwx 1 root root 7 Dec 16 08:58 srvlv -> ../dm-5 lrwxrwxrwx 1 root root 7 Dec 16 08:58 swaplv -> ../dm-7 lrwxrwxrwx 1 root root 7 Dec 16 08:58 usrlocallv -> ../dm-6 lrwxrwxrwx 1 root root 7 Dec 16 08:58 usrlv -> ../dm-1 lrwxrwxrwx 1 root root 7 Dec 16 08:58 varliblv -> ../dm-3 lrwxrwxrwx 1 root root 7 Dec 16 08:58 varlv -> ../dm-2 # -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954635 Title: subiquity crashes when attempting advanced network/disk configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1954635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954635] Re: subiquity crashes when attempting advanced network/disk configuration
** Attachment added: "Contents of /var/crash in crashed install" https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1954635/+attachment/5547285/+files/var.crash.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954635 Title: subiquity crashes when attempting advanced network/disk configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1954635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954635] Re: subiquity crashes when attempting advanced network/disk configuration
** Attachment added: "Contents of /var/log in crashed install" https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1954635/+attachment/5547284/+files/var.log.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954635 Title: subiquity crashes when attempting advanced network/disk configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1954635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954635] [NEW] subiquity crashes when attempting advanced network/disk configuration
Public bug reported: Subiquity for 20.04 crashes and a system install attempt fails when attempting to do an install with a complex network or disk configuration. When attempting an install with a semi-complex configuration (e.g. multiple network interfaces bonded together using LACP or multiple partitions with LVM, tmpfs, and swap), the installer will crash and fail. I am attempting an automated install using ISOs generated by the scripts at https://github.com/covertsh/ubuntu-autoinstall-generator and I am attempting to use the daily Ubuntu ISOs downloaded by that script. The user-data file that is attached fails with the current Ubuntu ISO download; however, it works with a daily ISO download that I made on 2021-12-03, so it appears that something broke on or after that date. ** Affects: subiquity (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Full user-data file" https://bugs.launchpad.net/bugs/1954635/+attachment/5547283/+files/generic-focal-p340-share.cfg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954635 Title: subiquity crashes when attempting advanced network/disk configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1954635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954582] [NEW] activation-mode directive not recognized in user-data file
Public bug reported: Using daily update image for 20.04 Placing activation-mode in the netplan section of the user-data file results in an error about an unknown token. After the automated install fails and you get dumped to a shell, no changes to files in /etc/netplan are needed to make the netplan try or netplan apply commands work without error. Documentation on this token are at https://netplan.io/reference/ (and elsewhere). ** Affects: subiquity (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/1954582 Title: activation-mode directive not recognized in user-data file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1954582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934735] Re: package gitolite3 3.6.11-2 failed to install/upgrade: installed gitolite3 package post-installation script subprocess returned error exit status 1
It looks like the root cause of this issue is that the post-install script uses the mktemp command when the current user is root and the default Ubuntu configuration sets $TMPDIR to /tmp/user/uid# so the temporary file that gets created is in /tmp/user/0. Later, the script switches to the gitolite3 user and tries to read the file that was created with mktemp (as the gitolite3 user, but that read fails because the gitolite3 user doesn't have permission to navigate the parent directories of the file. Changing permissions on the parent directories is a security problem, so the best solution is probably to set the $TMPDIR environment variable to some world-readable directory, such as /tmp, at the start of the post-install script. So, a one-line addition to the debian/postinst script probably fixes the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934735 Title: package gitolite3 3.6.11-2 failed to install/upgrade: installed gitolite3 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gitolite3/+bug/1934735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932525] Re: This bug is back on my pc - bug #1722481 Systemd Sync twice at shutdown
I am seeing something similar on 20.04. If my network fails and I have any network filesystems mounted (including nfs3 or nfs4 via autofs or iSCSI via fstab) when I issue a shutdown or reboot command, then I am likely to have a 10+ minute delay after the console displays that it has reached target shutdown. The console will then cycle through displaying information about each filesystem, such as the fact that the system is trying to unmount it, the unmount failed, and it is now forcibly killing processes. While I have not looked at the source, the timing of the console messages would imply that the process to unmount filesystems and kill processes is single-threaded, as there is a significant delay as it goes through this process with each filesystem. After it has cycled through all filesystems, it then slowly cycles through each filesystem again. Unfortunately, the logging system has already shut down by the time any of this happens, so I have no logs in journald or syslog to submit in relationship to this issue. Can the process be fixed to only cycle through each filesystem once, and also to attempt to do multiple filesystems simultaneously so that, at worst, I only have to wait through one timeout cycle? I could possibly see a reason that you might need to wait the timeout multiple times in the event of nested remote filesystems (e.g. if every level of /dont/try/this/at/home was a different filesystem on non-local disk), but that is not the configuration that I have. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932525 Title: This bug is back on my pc - bug #1722481 Systemd Sync twice at shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1932525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 95925] Re: debsecan should be either adjusted (for ubuntu) or removed
The unofficial database proposed in https://bugs.launchpad.net/ubuntu/+source/debsecan/+bug/95925/comments/12 appears to work. It's at least a major improvement on the current situation. I'd suggest that Ubuntu officially adopt the server-side tool and that appropriate updates are made to the defaults distributed with the package so that writing manual overrides to SUITE and SOURCE are not needed in /etc/default/debsecan to get usable results. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/95925 Title: debsecan should be either adjusted (for ubuntu) or removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debsecan/+bug/95925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 95925] Re: debsecan should be either adjusted (for ubuntu) or removed
** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/95925 Title: debsecan should be either adjusted (for ubuntu) or removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debsecan/+bug/95925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953212] [NEW] easygit homepage returns 404 error
Public bug reported: The project homepage listed in easygit packaging returns a 404 error. The package info as shown by apt, aptitude, etc. lists a URL that returns a 404, and the upstream-source listed in /usr/share/doc/easygit/copyright also has this problem. It appears that https://people.gnome.org/~newren/eg/ may be the correct URL. $ apt show easygit Package: easygit Version: 0.99-2 Priority: optional Section: universe/vcs Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian QA Group Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 291 kB Depends: perl:any, git-core, less, perl Homepage: http://www.gnome.org/~newren/eg/ Download-Size: 66.9 kB APT-Manual-Installed: yes APT-Sources: http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages Description: git for mere mortals In short, Easy GIT is a single-file wrapper script for git, designed to make git easy to learn and use. . Features: * eg focuses on documentation and examples * eg removes many principle-of-least-surprise violations that catch git newbies unaware * eg provides subcommands that are a natural extension of capabilities users know from cvs/svn (eg also takes care to make sure the modifications to its subcommands are easily discoverable and error-avoiding for existing git users as well!) ** Affects: easygit (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/1953212 Title: easygit homepage returns 404 error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/easygit/+bug/1953212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952901] [NEW] default ciderwebmail-uwsgi.conf breaks Apache
Public bug reported: Package: ciderwebmail Version: 1.05+20191006-1 OS: Ubuntu 20.04.3 LTS The /etc/apache2/conf-enabled/ciderwebmail-uwsgi.conf file that is shipped with ciderwebmail breaks Apache when it is enabled. Apache fails with: apachectl[69192]: AH00526: Syntax error on line 42 of /etc/apache2/conf-enabled/ciderwebmail-uwsgi.conf: apachectl[69192]: Invalid command 'ProxyPass', perhaps misspelled or defined by a module not included in the server configuration This happens after running "a2enconf ciderwebmail-uwsgi" Related upstream bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=963880 ** Affects: ciderwebmail (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/1952901 Title: default ciderwebmail-uwsgi.conf breaks Apache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ciderwebmail/+bug/1952901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952164] Re: cups.path repeatedly goes into systemd failed state
Discovered this was a system-wide problem, not specifically related to cups. Backup program was holding open a very high number if inotify watches and this was causing issues for other programs (including cups). Solution was to add a conf file in /etc/sysctl.d that set a higher value for fs.inotify.max_user_watches than the default (and then force a reload). In my case, this seems to work: echo "fs.inotify.max_user_watches=131072" >> /etc/sysctl.d/999-local.conf sysctl -p /etc/sysctl.d/999-local.conf Note that this solution may cause other issues on systems with low memory. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952164 Title: cups.path repeatedly goes into systemd failed state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1952164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952164] Re: cups.path repeatedly goes into systemd failed state
** Changed in: cups (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952164 Title: cups.path repeatedly goes into systemd failed state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1952164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952164] [NEW] cups.path repeatedly goes into systemd failed state
Public bug reported: cups.path is repeatedly entering a failed state in systemd. Attempts to restart the unit or even reboot the machine are, at best, temporary solutions. # systemctl status cups.path ● cups.path - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.path; enabled; vendor preset: enabled) Active: failed (Result: resources) Triggers: ● cups.service Nov 24 04:33:31 kangaroo.unclet.net systemd[1]: Started CUPS Scheduler. Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed to enter waiting state: No space left on device Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed with result 'resources'. # journalctl -u cups.path -- Logs begin at Tue 2021-11-23 22:54:38 EST, end at Wed 2021-11-24 21:42:42 EST. -- Nov 23 22:54:51 kangaroo.unclet.net systemd[1]: Started CUPS Scheduler. Nov 23 23:19:17 kangaroo.unclet.net systemd[1]: cups.path: Failed to enter waiting state: No space left on device Nov 23 23:19:17 kangaroo.unclet.net systemd[1]: cups.path: Failed with result 'resources'. -- Reboot -- Nov 24 04:33:31 kangaroo.unclet.net systemd[1]: Started CUPS Scheduler. Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed to enter waiting state: No space left on device Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed with result 'resources'. Despite what the log messages suggest, none of my (non-snap) filesystems are full (or even close to full): # df Filesystem 1K-blocks Used Available Use% Mounted on udev 32731616 032731616 0% /dev tmpfs 6556256 2536 6553720 1% /run /dev/mapper/kangaroovg-rootlv 5095040553996 4262516 12% / /dev/disk/by-id/dm-uuid-LVM-kxWkbFRXPo6GoeQURytO8JUpXOtGnGzNRQG28DNWnEi0JYl1Vkx1r7uvSiDwfZDb 20511312 724339212202960 38% /usr tmpfs 32781264 102432780240 1% /dev/shm tmpfs 5120 45116 1% /run/lock tmpfs 32781264 032781264 0% /sys/fs/cgroup none 4194304 3504 4190800 1% /tmp /dev/mapper/kangaroovg-varlv 5095040 1743876 3072636 37% /var /dev/nvme1n1p2 999320246420 684088 27% /boot /dev/mapper/kangaroovg-srvlv 5095040 20520 4795992 1% /srv /dev/mapper/kangaroovg-usrlocallv 5095040 31820 4784692 1% /usr/local /dev/mapper/kangaroovg-homelv 51343840 1300229235703724 27% /home /dev/mapper/kangaroovg-varliblv 5095040 1306604 3509908 28% /var/lib /dev/nvme1n1p1 523248 5360 517888 2% /boot/efi /dev/loop0 56832 56832 0 100% /snap/core18/2128 /dev/loop2 33152 33152 0 100% /snap/snapd/12883 /dev/loop1 72064 72064 0 100% /snap/lxd/21029 /dev/mapper/disharmony--kangaroo--qsan--vg-disharmony--kangaroo--qsan--lv 5325329320 198368460 4858509228 4% /srv/disharmony /dev/mapper/git--kangaroo--qsan--vg-git--kangaroo--qsan--lv 1055836596 77852 1002055476 1% /srv/git /dev/mapper/qsaniscsiunisonvg-unisonlv 5366618112 385871460 4980746652 8% /srv/unison /dev/mapper/qsaniscsilinuxbackupvg-linuxbackuplv 5366618112 96643028 5269975084 2% /srv/linux-backup /dev/mapper/qsaniscsisystemarchivevg-systemarchivelv 5366618112 745069628 4621548484 14% /srv/system-archive tmpfs
[Bug 1951920] [NEW] revise dependencies of munin to accept either munin-node or munin-node-c
Public bug reported: On a 20.04 system, attempting to install the packages munin and munin- node-c with aptitude fails, as munin recommends munin-node, but munin- node and munin-node-c conflict. Since both munin-node and munin-node-c provide the same function, the recommendation of the munin package should be adjusted to recommend either munin-node or munin-node-c. Expected result: aptitude install munin munin-node-c does show any conflicting dependencies. Acutal result: # aptitude install munin munin-node-c ... The following packages have unmet dependencies: munin-node-c : Conflicts: munin-node but 2.0.56-1ubuntu1 is to be installed The following actions will resolve these dependencies: Keep the following packages at their current version: 1) munin-node [Not Installed] Leave the following dependencies unresolved: 2) munin recommends munin-node Accept this solution? [Y/n/q/?] q ** Affects: munin (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/1951920 Title: revise dependencies of munin to accept either munin-node or munin- node-c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/1951920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946312] [NEW] nvidia: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1.
Public bug reported: On 20.04, I'm getting repeated errors on my system when the nvdidia drivers are installed. This sequence of errors is logged multiple times per second: Oct 7 01:45:29 kangaroo systemd-udevd[499101]: nvidia: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Oct 7 01:45:29 kangaroo kernel: [26851.518031] nvidia-nvlink: Nvlink Core is being initialized, major device number 510 Oct 7 01:45:29 kangaroo kernel: [26851.518035] NVRM: The NVIDIA probe routine was not called for 1 device(s). Oct 7 01:45:29 kangaroo kernel: [26851.518590] NVRM: This can occur when a driver such as: Oct 7 01:45:29 kangaroo kernel: [26851.518590] NVRM: nouveau, rivafb, nvidiafb or rivatv Oct 7 01:45:29 kangaroo kernel: [26851.518590] NVRM: was loaded and obtained ownership of the NVIDIA device(s). Oct 7 01:45:29 kangaroo kernel: [26851.518590] NVRM: Try unloading the conflicting kernel module (and/or Oct 7 01:45:29 kangaroo kernel: [26851.518590] NVRM: reconfigure your kernel without the conflicting Oct 7 01:45:29 kangaroo kernel: [26851.518590] NVRM: driver(s)), then try loading the NVIDIA kernel module Oct 7 01:45:29 kangaroo kernel: [26851.518590] NVRM: again. Oct 7 01:45:29 kangaroo kernel: [26851.518591] NVRM: No NVIDIA devices probed. Oct 7 01:45:29 kangaroo kernel: [26851.518746] nvidia-nvlink: Unregistered the Nvlink Core, major device number 510 Multiple systemd services report failures: root@kangaroo:~# systemctl list-units --state=failed UNITLOAD ACTIVE SUBDESCRIPTION ● nvidia-persistenced.service loaded failed failed NVIDIA Persistence Daemon ● plymouth-read-write.service loaded failed failed Tell Plymouth To Write Out Runtime Data ● systemd-udev-settle.service loaded failed failed udev Wait for Complete Device Initialization ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-video-nvidia-465 (not installed) ProcVersionSignature: Ubuntu 5.10.0-1049.51-oem 5.10.52 Uname: Linux 5.10.0-1049-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckMismatches: ./pool/main/l/linux-hwe-5.11/linux-modules-extra-5.11.0-34-generic_5.11.0-34.36~20.04.1_amd64.deb CasperMD5CheckResult: fail Date: Thu Oct 7 01:43:15 2021 InstallationDate: Installed on 2021-10-06 (1 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210914) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-470 (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/1946312 Title: nvidia: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946312] Re: nvidia: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1.
** Attachment added: "Output of lshw" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946312/+attachment/5531190/+files/lshw -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946312 Title: nvidia: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940603] Re: postfix/smtpd: fatal: no SASL authentication
That change to the file does seem to prevent the error, and I appreciate the help with my immediate problem. I'm still wondering if having the program crash as it did without generating a very useful error message is desirable behavior. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940603 Title: postfix/smtpd: fatal: no SASL authentication To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1940603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940603] Re: postfix/smtpd: fatal: no SASL authentication
Any more info you need? I was trying to follow the official Ubuntu server guide ( https://ubuntu.com/server/docs/mail-postfix ) with only a few deviations for things like a different location for SSL files. Are there more problems with that guide? Earlier in this item, you suggested moving authenticated connects off of port 25l but that doesn't happen in thus guide. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940603 Title: postfix/smtpd: fatal: no SASL authentication To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1940603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940603] Re: postfix/smtpd: fatal: no SASL authentication
** Attachment added: "main.cf" https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1940603/+attachment/5520588/+files/main.cf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940603 Title: postfix/smtpd: fatal: no SASL authentication To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1940603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940603] Re: postfix/smtpd: fatal: no SASL authentication
** Attachment added: "master.cf" https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1940603/+attachment/5520589/+files/master.cf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940603 Title: postfix/smtpd: fatal: no SASL authentication To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1940603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940603] Re: postfix/smtpd: fatal: no SASL authentication
I don't see a 220 message with the nc command either.
State Recv-QSend-Q Local Address:PortPeer Address:Port
Process
LISTEN0 1127.0.0.1:246970.0.0.0:*
users:(("IDrive:CDP-serv",pid=15790,fd=4))
LISTEN0 1000.0.0.0:25 0.0.0.0:*
users:(("master",pid=2515,fd=13))
LISTEN0 4096 0.0.0.0:4000 0.0.0.0:*
users:(("rpc.statd",pid=3079,fd=9))
LISTEN0 1000.0.0.0:993 0.0.0.0:*
users:(("dovecot",pid=1471,fd=35))
LISTEN0 1000.0.0.0:143 0.0.0.0:*
users:(("dovecot",pid=1471,fd=33))
LISTEN0 4096 0.0.0.0:111 0.0.0.0:*
users:(("rpcbind",pid=1103,fd=4),("systemd",pid=1,fd=237))
LISTEN0 4096 127.0.0.53%lo:53 0.0.0.0:*
users:(("systemd-resolve",pid=1137,fd=13))
LISTEN0 1280.0.0.0:22 0.0.0.0:*
users:(("sshd",pid=1490,fd=3))
LISTEN0 5127.0.0.1:631 0.0.0.0:*
users:(("cupsd",pid=8958,fd=7))
LISTEN0 100 [::]:25 [::]:*
users:(("master",pid=2515,fd=14))
LISTEN0 4096 [::]:4000[::]:*
users:(("rpc.statd",pid=3079,fd=11))
LISTEN0 100 [::]:993 [::]:*
users:(("dovecot",pid=1471,fd=36))
LISTEN0 100 [::]:143 [::]:*
users:(("dovecot",pid=1471,fd=34))
LISTEN0 4096 [::]:111 [::]:*
users:(("rpcbind",pid=1103,fd=6),("systemd",pid=1,fd=239))
LISTEN0 128 [::]:22 [::]:*
users:(("sshd",pid=1490,fd=4))
LISTEN0 5[::1]:631 [::]:*
users:(("cupsd",pid=8958,fd=6))
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940603
Title:
postfix/smtpd: fatal: no SASL authentication
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1940603/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940603] Re: postfix/smtpd: fatal: no SASL authentication
I didn't think the sasl2-bin package was needed, but someone else suggested I try adding it. Even with the settings that I had, shouldn't I have seen some messages from the server on the telnet connection? (e.g. remote mail server connecting to send mail to an address where this system is the final destination, so no authentication is attempted) If I telnet to port 25 on other servers, I get a 220 message, and then it waits for some command. On this system, I get no message from the server, and the connection is closed within about a second. ** Changed in: postfix (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/1940603 Title: postfix/smtpd: fatal: no SASL authentication To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1940603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940603] [NEW] postfix/smtpd: fatal: no SASL authentication
Public bug reported:
I'm trying to setup a combination IMAP/SMTP server using Dovecot and
Postfix on a 20.04 system. After attempting to setup SASL
authentication for postfix, the system fails with a postfix/smtpd:
fatal: no SASL authentication mechanisms whenever any SMTP connection is
attempted (either via a program like Thunderbird or telnet localhost
25). I'm trying to use the guide at
https://ubuntu.com/server/docs/mail-postfix, but even with some of the
debug settings enabled, I'm still not seeing a more useful log message.
What's wrong?
My configuration:
root@kangaroo:~# apt list --installed | egrep 'postfix|dovecot|sasl'
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
dovecot-core/focal-updates,focal-security,now 1:2.3.7.2-1ubuntu3.4 amd64
[installed]
dovecot-imapd/focal-updates,focal-security,now 1:2.3.7.2-1ubuntu3.4 amd64
[installed]
libauthen-sasl-perl/focal,now 2.1600-1 all [installed,automatic]
libsasl2-2/focal,now 2.1.27+dfsg-2 amd64 [installed,automatic]
libsasl2-dev/focal,now 2.1.27+dfsg-2 amd64 [installed]
libsasl2-modules-db/focal,now 2.1.27+dfsg-2 amd64 [installed,automatic]
libsasl2-modules/focal,now 2.1.27+dfsg-2 amd64 [installed,automatic]
postfix/focal-updates,now 3.4.13-0ubuntu1 amd64 [installed]
sasl2-bin/focal,now 2.1.27+dfsg-2 amd64 [installed]
root@kangaroo:~# dovecot -n
# 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.7.2 ()
# OS: Linux 5.10.0-1038-oem x86_64 Ubuntu 20.04.2 LTS
# Hostname: kangaroo.unclet.net
auth_debug = yes
auth_debug_passwords = yes
auth_mechanisms = plain login
mail_location = mbox:~/mail:INBOX=/var/mail/%u
mail_privileged_group = mail
namespace inbox {
inbox = yes
location =
mailbox Drafts {
special_use = \Drafts
}
mailbox Junk {
special_use = \Junk
}
mailbox Sent {
special_use = \Sent
}
mailbox "Sent Messages" {
special_use = \Sent
}
mailbox Trash {
special_use = \Trash
}
prefix =
}
passdb {
driver = pam
}
protocols = " imap"
service auth {
unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0660
user = postfix
}
}
ssl_cert =
kangaroo.unclet.net[127.0.0.1]: 220 kangaroo.unclet.net ESMTP Postfix (Ubuntu)
Aug 17 04:07:21 kangaroo postfix/smtpd[46495]: xsasl_dovecot_server_create:
SASL service=smtp, realm=(null)
Aug 17 04:07:21 kangaroo postfix/smtpd[46495]: name_mask: noanonymous
Aug 17 04:07:21 kangaroo postfix/smtpd[46495]: name_mask: noplaintext
Aug 17 04:07:21 kangaroo postfix/smtpd[46495]: xsasl_dovecot_server_connect:
Connecting
Aug 17 04:07:21 kangaroo dovecot: auth: Debug: Loading modules from directory:
/usr/lib/dovecot/modules/auth
Aug 17 04:07:21 kangaroo dovecot: auth: Debug: Module loaded:
/usr/lib/dovecot/modules/auth/lib20_auth_var_expand_crypt.so
Aug 17 04:07:21 kangaroo dovecot: auth: Debug: Read auth token secret from
/var/run/dovecot/auth-token-secret.dat
Aug 17 04:07:21 kangaroo postfix/smtpd[46495]: xsasl_dovecot_server_connect:
auth reply: VERSION?1?2
Aug 17 04:07:21 kangaroo postfix/smtpd[46495]: xsasl_dovecot_server_connect:
auth reply: MECH?PLAIN?plaintext
Aug 17 04:07:21 kangaroo postfix/smtpd[46495]: name_mask: plaintext
Aug 17 04:07:21 kangaroo postfix/smtpd[46495]: xsasl_dovecot_server_connect:
auth reply: MECH?LOGIN?plaintext
Aug 17 04:07:21 kangaroo dovecot: auth: Debug: auth client connected (pid=0)
Aug 17 04:07:21 kangaroo postfix/smtpd[46495]: name_mask: plaintext
Aug 17 04:07:21 kangaroo postfix/smtpd[46495]: xsasl_dovecot_server_connect:
auth reply: SPID?46497
Aug 17 04:07:21 kangaroo postfix/smtpd[46495]: xsasl_dovecot_server_connect:
auth reply: CUID?1
Aug 17 04:07:21 kangaroo postfix/smtpd[46495]: xsasl_dovecot_server_connect:
auth reply: COOKIE?f1df4b151ab753934e42c4baaa1d2620
Aug 17 04:07:21 kangaroo postfix/smtpd[46495]: xsasl_dovecot_server_connect:
auth reply: DONE
Aug 17 04:07:21 kangaroo postfix/smtpd[46495]:
xsasl_dovecot_server_mech_filter: skip mechanism: PLAIN
Aug 17 04:07:21 kangaroo postfix/smtpd[46495]:
xsasl_dovecot_server_mech_filter: skip mechanism: LOGIN
Aug 17 04:07:21 kangaroo postfix/smtpd[46495]: fatal: no SASL authentication
mechanisms
Aug 17 04:07:22 kangaroo postfix/master[26205]: warning: process
/usr/lib/postfix/sbin/smtpd pid 46495 exit status 1
Aug 17 04:07:22 kangaroo postfix/master[26205]: warning:
/usr/lib/postfix/sbin/smtpd: bad command startup -- throttling
Although this step was not in the install guide I've referenced, I've
tried adding sasl2-bin and editing /etc/default/saslauthd:
root@kangaroo:~# grep -v ^\# /etc/default/saslauthd |grep -v ^\$
START=yes
DESC="SASL Authentication Daemon"
NAME="saslauthd"
MECHANISMS="pam"
MECH_OPTIONS=""
THREADS=5
OPTIONS="-c -m /var/run/saslauthd"
root@kangaroo:~# systemctl is-active saslauthd
active
** Affects: postfix (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
[Bug 1823521] Re: on_ac_power returns 1 if battery is not present
I'm having a similar issue on Ubuntu 20.04 on a Lenovo P340, which is a desktop workstation system and thus doesn't even have any capability for battery operation without an external UPS. I'm attaching a copy of selected directories in /sys and /proc that the script inspects. ** Attachment added: "Tar of selected directories in /sys and /proc" https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1823521/+attachment/5515514/+files/on_ac_power_bug.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823521 Title: on_ac_power returns 1 if battery is not present To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-power-manager/+bug/1823521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938672] [NEW] Incomplete information in AppArmorProfiles web documentation
Public bug reported: The table of profiles on the page https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles does not have any of the footnote entries for 20.04 or 20.10. Since these footnotes are present in the table for earlier versions of Ubuntu, it implies that there have been multiple changes to AppArmor profiles in 20.04. Example: The table shows that an AppArmor rule set exists for Apache2. For 18.04 (and earlier) releases, the table footnotes indicates that these rules are not enabled by default. The lack of footnote entries in the 20.04 (and later) release columns suggest that the AppArmor rules are enabled by default. However, even after installing the apache2 and libapache2-mod-apparmor packages, aa-status indicates that no AppArmor rules are enforced for Apache. Lengthy comments at the beginning of the /etc/apparmor.d/usr.sbin.apache2 file indicate that this is the intended behavior, and thus the table on the page mentioned in the first paragraph is incomplete. Similar issues exist for multiple other table entries (Firefox, rsyslogd, etc.). This is being reported as a bug because the wiki page is marked as immutable. ** Affects: apparmor (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/1938672 Title: Incomplete information in AppArmorProfiles web documentation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1938672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937889] [NEW] weather not working with airport codes
Public bug reported: An example given in the man page for weather: weather rdu fails. taft@kangaroo:~$ weather rdu Searching via airport... No IATA/FAA airport code "rdu" in the /usr/share/weather-util/airports.gz file. I have tried multiple other airport codes, and none of them seem to work: taft@kangaroo:~$ weather dfw Searching via airport... No IATA/FAA airport code "dfw" in the /usr/share/weather-util/airports.gz file. taft@kangaroo:~$ weather nyc Searching via airport... No IATA/FAA airport code "nyc" in the /usr/share/weather-util/airports.gz file. taft@kangaroo:~$ weather lax Searching via airport... No IATA/FAA airport code "lax" in the /usr/share/weather-util/airports.gz file. taft@kangaroo:~$ weather lhr Searching via airport... No IATA/FAA airport code "lhr" in the /usr/share/weather-util/airports.gz file. taft@kangaroo:~$ weather hel Searching via airport... No IATA/FAA airport code "hel" in the /usr/share/weather-util/airports.gz file. taft@kangaroo:~$ weather syd Searching via airport... No IATA/FAA airport code "syd" in the /usr/share/weather-util/airports.gz file. ** Affects: weather-util (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/1937889 Title: weather not working with airport codes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/weather-util/+bug/1937889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936273] [NEW] apt not respecting Ignore-Files-Silently directive
Public bug reported: I have a configuration management system that stores a backup copy of files that it updates with a suffix based upon the date that the file is updated (.-MM-DD) In Ubuntu 20.04, I have added a file 00ignore to the /etc/apt/apt.conf directory. The contents of the file are one line: Dir::Ignore-Files-Silently:: "\.[12][0-9][0-9][0-9]-[01][0-9]-[0-3][0-9]$"; The system appears to read the file, but doesn't seem to process it, as apt and related programs still spit out warnings. # apt-config dump |grep Ignore Dir::Ignore-Files-Silently ""; Dir::Ignore-Files-Silently:: "~$"; Dir::Ignore-Files-Silently:: "\.disabled$"; Dir::Ignore-Files-Silently:: "\.bak$"; Dir::Ignore-Files-Silently:: "\.dpkg-[a-z]+$"; Dir::Ignore-Files-Silently:: "\.ucf-[a-z]+$"; Dir::Ignore-Files-Silently:: "\.save$"; Dir::Ignore-Files-Silently:: "\.orig$"; Dir::Ignore-Files-Silently:: "\.distUpgrade$"; Dir::Ignore-Files-Silently:: "\.[12][0-9][0-9][0-9]-[01][0-9]-[0-3][0-9]$"; N: Ignoring file '99unclet-override.2021-06-15' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension N: Ignoring file '00unclet.2021-06-18' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension Note: aptitude does not display this warning, although many other apt- related programs do (e.g. apt, apt-get, apt-config). ** 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/1936273 Title: apt not respecting Ignore-Files-Silently directive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1936273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934735] [NEW] package gitolite3 3.6.11-2 failed to install/upgrade: installed gitolite3 package post-installation script subprocess returned error exit status 1
Public bug reported: Attempt to install gitolite3 fails. Directory path set in debconf for gitolite3/adminkey prior to install attempt. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: gitolite3 3.6.11-2 ProcVersionSignature: Ubuntu 5.10.0-1034.35-oem 5.10.41 Uname: Linux 5.10.0-1034-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckMismatches: ./pool/main/l/linux-hwe-5.8/linux-modules-extra-5.8.0-59-generic_5.8.0-59.66~20.04.1_amd64.deb CasperMD5CheckResult: fail Date: Mon Jul 5 07:05:53 2021 ErrorMessage: installed gitolite3 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-07-05 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210627) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: gitolite3 Title: package gitolite3 3.6.11-2 failed to install/upgrade: installed gitolite3 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gitolite3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package 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/1934735 Title: package gitolite3 3.6.11-2 failed to install/upgrade: installed gitolite3 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gitolite3/+bug/1934735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908090] Re: ubuntu 20.04 kdump fails
Are you sure you have this bug filed against the correct package? At a glance, it looks like you should file it against linux-meta (see https://packages.ubuntu.com/focal/linux-crashdump ) kexec-tools "provides tools to load a kernel into memory and then "reboot" directly into that kernel using the kexec system call, bypassing the normal boot process." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908090 Title: ubuntu 20.04 kdump fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1908090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933711] Re: defining tmpfs /tmp in autoinstall config fails
The proposed fix works for me, both in the both in the simple example I posted, as well as a more complex configuration that I didn't post. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933711 Title: defining tmpfs /tmp in autoinstall config fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1933711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933711] [NEW] defining tmpfs /tmp in autoinstall config fails
Public bug reported: Attempting to creat a tmpfs /tmp partition with the Ubuntu 20.04 autoinstaller fails with the error: __init__() missing 1 required positional argument: 'device' The relevant section of the user-data file I'm attempting is: - id: tmpfs1 type: mount spec: "none" path: "/tmp" options: size=4194304 fstype: "tmpfs" This section is copied directly from https://curtin.readthedocs.io/en/latest/topics/storage.html (changing the path). The full file is attached. Autoinstall succeeds if all of the lines listed above are deleted. I'm using the daily ISO autoinstall image downloaded using the script at https://github.com/covertsh/ubuntu-autoinstall-generator . ** Affects: subiquity (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Full user-data file" https://bugs.launchpad.net/bugs/1933711/+attachment/5507186/+files/user-data -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933711 Title: defining tmpfs /tmp in autoinstall config fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1933711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933711] Re: defining tmpfs /tmp in autoinstall config fails
** Attachment added: "Log files from failed install" https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1933711/+attachment/5507187/+files/crash-logs.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933711 Title: defining tmpfs /tmp in autoinstall config fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1933711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923080] Re: ubuntu upgrade to 20 from 18 .04.5 fails. Error message is indeterminate.
It would be useful if that message or something similar to what m-hample stated was displayed. It would also be useful to provide a link to the official repository names in the error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923080 Title: ubuntu upgrade to 20 from 18 .04.5 fails. Error message is indeterminate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1923080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923080] Re: ubuntu upgrade to 20 from 18 .04.5 fails. Error message is indeterminate.
I got past the issue by removing all the packages listed here for my distro. Upgrade is now commencing. https://www.ubuntuupdates.org/ppa/xorg-edgers?dist=bionic=87=1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923080 Title: ubuntu upgrade to 20 from 18 .04.5 fails. Error message is indeterminate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1923080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923080] [NEW] ubuntu upgrade to 20 from 18 .04.5 fails. Error message is indeterminate.
Public bug reported: Ubuntu 18.04.5 LTS upgrading to latest LTS version. Expecting the upgrade to proceed or at least give me a useful error, however it doesn't display an error. Instead it just states "Could not calculate the upgrade. An unresolvable problem occurred while calculating the upgrade. If none of this applies report the bug. Since there is no problem listed with the error message, I would expect one to be listed. Since none of the error does apply (nothing listed) I'm reporting it as a bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.42 ProcVersionSignature: Ubuntu 4.15.0-140.144-generic 4.15.18 Uname: Linux 4.15.0-140-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Apr 8 13:50:31 2021 InstallationDate: Installed on 2017-10-13 (1273 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) 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 2021-04-08 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923080 Title: ubuntu upgrade to 20 from 18 .04.5 fails. Error message is indeterminate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1923080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917304] Re: Firefox bookmark separators not showing in budgie
Issue still exists after going to Budgie Welcome -> Themes -> Pocillo -> Apply Makeover but not Budgie Welcome -> Themes -> QogirBudgie -> Apply Makeover (i.e. QogirBudgie renders separators.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917304 Title: Firefox bookmark separators not showing in budgie To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acroread/+bug/1917304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917304] Re: Firefox bookmark separators not showing in budgie
expected-menu.png Shows bookmarks menu as rendered by "standard" Ubuntu (GNOME) - an appearance similar to this is what I expected. ** Attachment added: "expected-menu.png" https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1917304/+attachment/5471479/+files/expected-menu.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917304 Title: Firefox bookmark separators not showing in budgie To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acroread/+bug/1917304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917304] Re: Firefox bookmark separators not showing in budgie
menu-editor.png Shows separators exist in Firefox config (from Budgie system) ** Attachment added: "menu-editor.png" https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1917304/+attachment/5471478/+files/menu-editor.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917304 Title: Firefox bookmark separators not showing in budgie To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acroread/+bug/1917304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917304] Re: Firefox bookmark separators not showing in budgie
budgie-menu.png: Bookmarks menu as rendered in Budgie ** Attachment added: "budgie-menu.png" https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1917304/+attachment/5471477/+files/budgie-menu.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917304 Title: Firefox bookmark separators not showing in budgie To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acroread/+bug/1917304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917304] [NEW] Firefox bookmark separators not showing in budgie
Public bug reported: In Ubuntu Budgie 20.04.2, bookmarks separators do not appear within Firefox bookmarks menu. This issue is being logged against Budgie, rather than Firefox because it does not appear in other variants of Ubuntu 20.04.2 (e.g. "standard"/GNOME, Ubuntu-Mate, Lubuntu) How to reproduce: Launch Firefox Go to Customize Make sure Menu bar is enabled Save settings Go to Bookmarks - Show All Bookmarks Verify that the bookmarks menu area shows several bookmarks/folders and separators (create them if they don't exist.) Open the Bookmarks menu and see that no separators appear Versions installed: budgie-desktop-environment 0.13.7 ubuntu-budgie-desktop 0.65 firefox 86.0+build3-0ubuntu0.20.04.1 ** Affects: acroread (Ubuntu) Importance: Undecided Status: Invalid ** Affects: budgie-desktop (Ubuntu) Importance: Undecided Status: Incomplete ** Also affects: budgie-desktop (Ubuntu) Importance: Undecided Status: New ** Changed in: acroread (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917304 Title: Firefox bookmark separators not showing in budgie To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acroread/+bug/1917304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894101] Re: ubuntu 20.04.1 installed with zfs root fails to boot after installing xen-hypervisor
The best solution may involve fixing grub-probe so it knows a ZFS filesystem. The attached patch is a simple workaround that worked on my 3 test systems. For example if the patch is downloaded to /tmp/grub2.patch You can install the patch like this: cd /etc/grub.d; sudo patch < /tmp/grub2.patch ** Patch added: "Test fix to work around grub-probe failure" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1894101/+attachment/5440778/+files/grub2.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894101 Title: ubuntu 20.04.1 installed with zfs root fails to boot after installing xen-hypervisor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1894101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894101] Re: ubuntu 20.04.1 installed with zfs root fails to boot after installing xen-hypervisor
In line 137 of file "10_linux":
rpool=`${grub_probe} --device ${GRUB_DEVICE} --target=fs_label
2>/dev/null || true`
The command run returns this error:
root@stream:/etc/grub.d# /usr/sbin/grub-probe --device /dev/nvme0n1p4
--target=fs_label
/usr/sbin/grub-probe: error: unknown filesystem.
The result makes ${rpool} NULL, and sets ${LINUX_ROOT_DEVICE} to
"ZFS=/ROOT/ubuntu_aaodxz"
This is clearly wrong and looks like the root cause of this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894101
Title:
ubuntu 20.04.1 installed with zfs root fails to boot after installing
xen-hypervisor
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1894101/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894101] Re: ubuntu 20.04.1 installed with zfs root fails to boot after installing xen-hypervisor
I have two different Ubuntu 20.04.1 systems using ZFS on root. Only one has Xen installed, but both have had this same problem with rpool missing from the grub.cfg and fail to boot after update-grub/grub- mkconfig is run. Both systems share an error during /etc/grub.d/30_os- prober: - System one ### BEGIN /etc/grub.d/30_os-prober ### device-mapper: reload ioctl on osprober-linux-nvme0n1p4 failed: Device or resource busy Command failed. ### END /etc/grub.d/30_os-prober ### - System two ### BEGIN /etc/grub.d/30_os-prober ### device-mapper: reload ioctl on osprober-linux-sda7 failed: Device or resource busy Command failed. ### END /etc/grub.d/30_os-prober ### I have uploaded the full log. ** Attachment added: "Log of grub-mkconfig" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1894101/+attachment/5440632/+files/grub-mkconfig.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894101 Title: ubuntu 20.04.1 installed with zfs root fails to boot after installing xen-hypervisor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1894101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894101] Re: ubuntu 20.04.1 installed with zfs root fails to boot after installing xen-hypervisor
I have now seen this problem without xen-hypervisor installed. With a ZFS root it also happened after using grub-customizer, and after a kernel update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894101 Title: ubuntu 20.04.1 installed with zfs root fails to boot after installing xen-hypervisor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1894101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902929] Re: grub-mkconfig fails to include zpool when using zfs & xen
*** This bug is a duplicate of bug 1894101 *** https://bugs.launchpad.net/bugs/1894101 ** This bug has been marked a duplicate of bug 1894101 ubuntu 20.04.1 installed with zfs root fails to boot after installing xen-hypervisor -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902929 Title: grub-mkconfig fails to include zpool when using zfs & xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1902929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894101] Re: ubuntu 20.04.1 installed with zfs root fails to boot after installing xen-hypervisor
This is my first bug report using bugs.launchpad.net and I did not know I could move the bug report to a different package. I have created a duplicate report, and don't see a way to close one of them. It was under the Xen package, but with more investigation it looks like it belongs in the grub2 package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894101 Title: ubuntu 20.04.1 installed with zfs root fails to boot after installing xen-hypervisor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1894101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894101] Re: ubuntu 20.04.1 installed with zfs root fails to boot after installing xen-hypervisor
The xen postinst script is using the update-grub command, which runs grub-mkconfig. Running grub-mkconfig produced this output: root@corona:~# grub-mkconfig -o /boot/grub/grub.cfg Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Sourcing file `/etc/default/grub.d/xen.cfg' Including Xen overrides from /etc/default/grub.d/xen.cfg WARNING: GRUB_DEFAULT changed to boot into Xen by default! Edit /etc/default/grub.d/xen.cfg to avoid this warning. Generating grub configuration file ... Found linux image: vmlinuz-5.4.0-52-generic in rpool/ROOT/ubuntu_69vvbr Found initrd image: initrd.img-5.4.0-52-generic in rpool/ROOT/ubuntu_69vvbr Found linux image: vmlinuz-5.4.0-51-generic in rpool/ROOT/ubuntu_69vvbr Found initrd image: initrd.img-5.4.0-51-generic in rpool/ROOT/ubuntu_69vvbr Found linux image: vmlinuz-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr Found initrd image: initrd.img-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr Found linux image: vmlinuz-5.4.0-47-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_4k3sjn Found initrd image: initrd.img-5.4.0-47-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_4k3sjn Found linux image: vmlinuz-5.4.0-45-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_4k3sjn Found initrd image: initrd.img-5.4.0-45-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_4k3sjn Found linux image: vmlinuz-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_4k3sjn Found initrd image: initrd.img-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_4k3sjn Found linux image: vmlinuz-5.4.0-47-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_7ur3n5 Found initrd image: initrd.img-5.4.0-47-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_7ur3n5 Found linux image: vmlinuz-5.4.0-45-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_7ur3n5 Found initrd image: initrd.img-5.4.0-45-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_7ur3n5 Found linux image: vmlinuz-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_7ur3n5 Found initrd image: initrd.img-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_7ur3n5 Found linux image: vmlinuz-5.4.0-48-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_l6bt3l Found initrd image: initrd.img-5.4.0-48-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_l6bt3l Found linux image: vmlinuz-5.4.0-47-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_l6bt3l Found initrd image: initrd.img-5.4.0-47-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_l6bt3l Found linux image: vmlinuz-5.4.0-45-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_l6bt3l Found initrd image: initrd.img-5.4.0-45-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_l6bt3l Found linux image: vmlinuz-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_l6bt3l Found initrd image: initrd.img-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_l6bt3l Found linux image: vmlinuz-5.4.0-48-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_3qeu07 Found initrd image: initrd.img-5.4.0-48-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_3qeu07 Found linux image: vmlinuz-5.4.0-47-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_3qeu07 Found initrd image: initrd.img-5.4.0-47-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_3qeu07 Found linux image: vmlinuz-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_3qeu07 Found initrd image: initrd.img-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_3qeu07 Found linux image: vmlinuz-5.4.0-48-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_bxegdn Found initrd image: initrd.img-5.4.0-48-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_bxegdn Found linux image: vmlinuz-5.4.0-47-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_bxegdn Found initrd image: initrd.img-5.4.0-47-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_bxegdn Found linux image: vmlinuz-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_bxegdn Found initrd image: initrd.img-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_bxegdn Found linux image: vmlinuz-5.4.0-48-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_61mm5b Found initrd image: initrd.img-5.4.0-48-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_61mm5b Found linux image: vmlinuz-5.4.0-47-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_61mm5b Found initrd image: initrd.img-5.4.0-47-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_61mm5b Found linux image: vmlinuz-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_61mm5b Found initrd image: initrd.img-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_61mm5b Found linux image: vmlinuz-5.4.0-48-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_uha13z Found initrd image: initrd.img-5.4.0-48-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_uha13z Found linux image: vmlinuz-5.4.0-47-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_uha13z Found initrd image: initrd.img-5.4.0-47-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_uha13z Found linux image: vmlinuz-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_uha13z Found initrd image: initrd.img-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_uha13z Found linux image:
[Bug 1894101] Re: ubuntu 20.04.1 installed with zfs root fails to boot after installing xen-hypervisor
This is looking like a problem with the grub package. ** Package changed: xen (Ubuntu) => grub2 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894101 Title: ubuntu 20.04.1 installed with zfs root fails to boot after installing xen-hypervisor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1894101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894101] Re: ubuntu 20.04.1 installed with zfs root fails to boot after installing xen-hypervisor
It looks like this is a problem with "grub-mkconfig". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894101 Title: ubuntu 20.04.1 installed with zfs root fails to boot after installing xen-hypervisor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1894101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902929] [NEW] grub-mkconfig fails to include zpool when using zfs & xen
Public bug reported: After installing 20.04.1 using the ZFS root option I installed Xen. When it rebooted it failed in initramfs with the error "No pool imported". I was able to boot the previous kernel. When I examined the /boot/grub/grub.cfg I found what looked like invalid "root=ZFS=" options like this: "root=ZFS=/ROOT/ubuntu_xx" The previous kernel that boots looks like this: "root=ZFS=rpool/ROOT/ubuntu_xx" As a test saved a copy and edited /boot/grub/grub.cfg adding the rpool to each "root=ZFS=" line where rpool was missing. This time I was able to boot the Xen kernel. The xen postinst script is using the update-grub command, which runs grub-mkconfig. Running grub-mkconfig produced this output: root@corona:~# grub-mkconfig -o /boot/grub/grub.cfg Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Sourcing file `/etc/default/grub.d/xen.cfg' Including Xen overrides from /etc/default/grub.d/xen.cfg WARNING: GRUB_DEFAULT changed to boot into Xen by default! Edit /etc/default/grub.d/xen.cfg to avoid this warning. Generating grub configuration file ... Found linux image: vmlinuz-5.4.0-52-generic in rpool/ROOT/ubuntu_69vvbr Found initrd image: initrd.img-5.4.0-52-generic in rpool/ROOT/ubuntu_69vvbr Found linux image: vmlinuz-5.4.0-51-generic in rpool/ROOT/ubuntu_69vvbr Found initrd image: initrd.img-5.4.0-51-generic in rpool/ROOT/ubuntu_69vvbr Found linux image: vmlinuz-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr Found initrd image: initrd.img-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr Found linux image: vmlinuz-5.4.0-47-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_4k3sjn Found initrd image: initrd.img-5.4.0-47-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_4k3sjn Found linux image: vmlinuz-5.4.0-45-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_4k3sjn Found initrd image: initrd.img-5.4.0-45-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_4k3sjn Found linux image: vmlinuz-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_4k3sjn Found initrd image: initrd.img-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_4k3sjn Found linux image: vmlinuz-5.4.0-47-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_7ur3n5 Found initrd image: initrd.img-5.4.0-47-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_7ur3n5 Found linux image: vmlinuz-5.4.0-45-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_7ur3n5 Found initrd image: initrd.img-5.4.0-45-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_7ur3n5 Found linux image: vmlinuz-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_7ur3n5 Found initrd image: initrd.img-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_7ur3n5 Found linux image: vmlinuz-5.4.0-48-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_l6bt3l Found initrd image: initrd.img-5.4.0-48-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_l6bt3l Found linux image: vmlinuz-5.4.0-47-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_l6bt3l Found initrd image: initrd.img-5.4.0-47-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_l6bt3l Found linux image: vmlinuz-5.4.0-45-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_l6bt3l Found initrd image: initrd.img-5.4.0-45-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_l6bt3l Found linux image: vmlinuz-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_l6bt3l Found initrd image: initrd.img-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_l6bt3l Found linux image: vmlinuz-5.4.0-48-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_3qeu07 Found initrd image: initrd.img-5.4.0-48-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_3qeu07 Found linux image: vmlinuz-5.4.0-47-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_3qeu07 Found initrd image: initrd.img-5.4.0-47-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_3qeu07 Found linux image: vmlinuz-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_3qeu07 Found initrd image: initrd.img-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_3qeu07 Found linux image: vmlinuz-5.4.0-48-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_bxegdn Found initrd image: initrd.img-5.4.0-48-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_bxegdn Found linux image: vmlinuz-5.4.0-47-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_bxegdn Found initrd image: initrd.img-5.4.0-47-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_bxegdn Found linux image: vmlinuz-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_bxegdn Found initrd image: initrd.img-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_bxegdn Found linux image: vmlinuz-5.4.0-48-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_61mm5b Found initrd image: initrd.img-5.4.0-48-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_61mm5b Found linux image: vmlinuz-5.4.0-47-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_61mm5b Found initrd image: initrd.img-5.4.0-47-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_61mm5b Found linux image: vmlinuz-5.4.0-42-generic in rpool/ROOT/ubuntu_69vvbr@autozsys_61mm5b Found initrd image: initrd.img-5.4.0-42-generic in
[Bug 1721987] Re: No sound from right audio channel
I was still having problems with my Lenovo Legion laptop, this is one of the pages where I stopped in and tried everything on it, to no avail. It looks like the specific issue here was fixed, and any other info I found on the internet was not working either. Turns out that by default, headphone jack had right channel turned all the way down! Here's what I did to fix: Open terminal window. Execute command: sudo alsamixer This is a terminal-based application that allows you to change audio output levels for different ports. You may need to press F6 to select your sound card -- mine was selected when I started the application. Basically Master and PCM all had both left and right channels maxed into the red zone. Headphones ONLY had the left channel. Press the right-arrow on your keyboard to go over to Headphones, then press the up-arrow repeatedly and the right channel level should increase, take it to the max with the left channel. Exit Alsa Mixer with the escape key. This fixed it but then the audio in the right channel, for whatever reason, was extremely quiet. I went into Ubuntu's basic sound settings window (Settings > Sound). I made sure I had the "Headphones - Built-in Audio" selected in the dropdown box for Output, then drug the balance slider all the way to the left and let go of mouse button. Then all the way to the right and let go of mouse button. Then back to the middle and let go of the mouse button. Now it was working and sounded great! I went back into alsamixer one more time, and noticed the right channel on the headphones had dropped a tiny notch compared to the left. I put it back to max, and exited Alsa Mixer. I now have no problems with my headset! If you're still struggling even though this bug fix was released a year ago, try my simple suggestion before you go all crazy editing files. It might save you many hours of internal screaming :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721987 Title: No sound from right audio channel To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1721987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900768] [NEW] Upgrade from 18.04 failed
Public bug reported: Was upgrading 18.04 to 20 and it won't upgrade ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.40 ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Oct 20 14:40:32 2020 InstallationDate: Installed on 2018-12-09 (681 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-10-20 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900768 Title: Upgrade from 18.04 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1900768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884295] Re: AttributeError: 'QWebEngineProfile' object has no attribute 'setUrlRequestInterceptor'
Seems we need that downstream too, then? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884295 Title: AttributeError: 'QWebEngineProfile' object has no attribute 'setUrlRequestInterceptor' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1884295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894101] [NEW] ubuntu 20.04.1 installed with zfs root fails to boot after installing xen-hypervisor
Public bug reported: After installing 20.04.1 using the ZFS root option I installed Xen. When it rebooted it failed in initramfs with the error "No pool imported". I was able to boot the previous kernel. When I examined the /boot/grub/grub.cfg I found what looked like invalid "root=ZFS=" options like this: "root=ZFS=/ROOT/ubuntu_xx" The previous kernel that boots looks like this: "root=ZFS=rpool/ROOT/ubuntu_xx" After looking in /etc/default/grub and /etc/grub.d I was unable to figure out why they were different and how I could change it. As a test saved a copy and edited /boot/grub/grub.cfg adding the rpool to each "root=ZFS=" line where rpool was missing. This time I was able to boot the Xen kernel. == How to reproduce the problem >From scratch install ubuntu 20.04.1 desktop, select ZFS as root option, then >install xen-hypervisor-4.11-amd64. It will fail to reboot because the grub root=ZFS argument is wrong. ** Affects: xen (Ubuntu) Importance: Undecided Status: New ** Tags: grub root rpool xen zfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894101 Title: ubuntu 20.04.1 installed with zfs root fails to boot after installing xen-hypervisor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1894101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890967] [NEW] Jumper EZpad touchpad registered as mouse
Public bug reported: The touchpad on my "Jumper EZPad S6 Pro" registers as a mouse and can not be disabled while typing. Diagnostics attached. FWIW I'd be content with a workrauond to disable while typing; otherwise I'm contnet w/ touchpad functionality. ** Affects: xserver-xorg-input-libinput (Ubuntu) Importance: Undecided Status: New ** Attachment added: "diagnostics" https://bugs.launchpad.net/bugs/1890967/+attachment/5400253/+files/bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890967 Title: Jumper EZpad touchpad registered as mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1890967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884295] Re: AttributeError: 'QWebEngineProfile' object has no attribute 'setUrlRequestInterceptor'
I have also encountered this issue: Parsing all content... CSSStyleDeclaration: Unexpected token, ignoring upto '$698: False;'. [9:11: $] CSSStyleDeclaration: Unexpected token, ignoring upto '$698: False;'. [16:12: $] CSSStyleDeclaration: Unexpected token, ignoring upto '$698: False;'. [18:12: $] 34% Running transforms on e-book... Merging user specified metadata... Detecting structure... Flattening CSS and remapping font sizes... Source base font size is 12.0pt Removing fake margins... Cleaning up manifest... Trimming unused files from manifest... Creating PDF Output... 67% Running PDF Output plugin The cover image has an id != "cover". Renaming to work around bug in Nook Color 68% Parsed all content for markup transformation 70% Completed markup transformation WebEngineContext used before QtWebEngine::initialize() or OpenGL context creation failed. Traceback (most recent call last): File "/usr/bin/ebook-convert", line 20, in sys.exit(main()) File "/usr/lib/calibre/calibre/ebooks/conversion/cli.py", line 401, in main plumber.run() File "/usr/lib/calibre/calibre/ebooks/conversion/plumber.py", line 1274, in run self.output_plugin.convert(self.oeb, self.output, self.input_plugin, File "/usr/lib/calibre/calibre/ebooks/conversion/plugins/pdf_output.py", line 188, in convert self.convert_text(oeb_book) File "/usr/lib/calibre/calibre/ebooks/conversion/plugins/pdf_output.py", line 253, in convert_text convert( File "/usr/lib/calibre/calibre/ebooks/pdf/html_writer.py", line 1195, in convert manager = RenderManager(opts, log, container.root) File "/usr/lib/calibre/calibre/ebooks/pdf/html_writer.py", line 279, in __init__ ans.setUrlRequestInterceptor(self.interceptor) AttributeError: 'QWebEngineProfile' object has no attribute 'setUrlRequestInterceptor' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884295 Title: AttributeError: 'QWebEngineProfile' object has no attribute 'setUrlRequestInterceptor' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1884295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1888994] Re: Display scale setting is not saved across reboot
Hello Dan, Yes it looks like the scale is 2 for the main monitor in both my single and dual monitor setups. There is a ~/.config/monitors.xml~ file created after I change the settings. On Tue, Jul 28, 2020 at 10:30 PM Daniel van Vugt <1888...@bugs.launchpad.net> wrote: > Thanks. And sorry I'm not very familiar with Budgie - it seems to be > related to gnome-shell but different. > > Regardless, your display scale should be stored in > ~/.config/monitors.xml along with all the display layout details. You > might want to look in there to check that a scale value of 2 is being > saved. Although it might look overly complicated as that file stores > *all* the different display configurations (different monitors plugged > in) your system has used in the past. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1888994 > > Title: > Display scale setting is not saved across reboot > > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > I set my scale setting to 200%. If I have to reboot the pc the > setting is not saved and must be set again. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: gnome-control-center 1:3.36.2-0ubuntu1 > ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 > Uname: Linux 5.4.0-42-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.4 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: Budgie:GNOME > Date: Sun Jul 26 08:42:34 2020 > ExecutablePath: /usr/bin/gnome-control-center > InstallationDate: Installed on 2020-06-29 (27 days ago) > InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > ProcEnviron: >LANGUAGE=en_US >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: gnome-control-center > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888994/+subscriptions > -- Thanks, Todd ** Attachment added: "monitors.xml" https://bugs.launchpad.net/bugs/1888994/+attachment/5397090/+files/monitors.xml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888994 Title: Display scale setting is not saved across reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1888994] Re: Display scale setting is not saved across reboot
Hello, Thanks for looking at this. It is a real laptop. An HP Envy. Installed from Ubuntu-Budgie 20.04 LTS amd64 [image: image.png]in Settings.txt is empty I included schemas.txt since the requested schema is not present. On Tue, Jul 28, 2020 at 2:15 AM Daniel van Vugt <1888...@bugs.launchpad.net> wrote: > Please run these commands: > > lspci -k > lspcik.txt > xrandr > xrandr.txt > journalctl -b0 > journal.txt > gsettings list-recursively org.gnome.shell > settings.txt > > and then attach the resulting text files. > > Also, is this a virtual machine or a real machine? > > > ** Changed in: gnome-shell (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1888994 > > Title: > Display scale setting is not saved across reboot > > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > I set my scale setting to 200%. If I have to reboot the pc the > setting is not saved and must be set again. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: gnome-control-center 1:3.36.2-0ubuntu1 > ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 > Uname: Linux 5.4.0-42-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.4 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: Budgie:GNOME > Date: Sun Jul 26 08:42:34 2020 > ExecutablePath: /usr/bin/gnome-control-center > InstallationDate: Installed on 2020-06-29 (27 days ago) > InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > ProcEnviron: >LANGUAGE=en_US >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: gnome-control-center > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888994/+subscriptions > -- Thanks, Todd ** Attachment added: "image.png" https://bugs.launchpad.net/bugs/1888994/+attachment/5396620/+files/image.png ** Attachment added: "lspcik.txt" https://bugs.launchpad.net/bugs/1888994/+attachment/5396621/+files/lspcik.txt ** Attachment added: "xrandr.txt" https://bugs.launchpad.net/bugs/1888994/+attachment/5396622/+files/xrandr.txt ** Attachment added: "journal.txt" https://bugs.launchpad.net/bugs/1888994/+attachment/5396623/+files/journal.txt ** Attachment added: "schemas.txt" https://bugs.launchpad.net/bugs/1888994/+attachment/5396624/+files/schemas.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888994 Title: Display scale setting is not saved across reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888994] [NEW] Display scale setting is not saved across reboot
Public bug reported: I set my scale setting to 200%. If I have to reboot the pc the setting is not saved and must be set again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Sun Jul 26 08:42:34 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-06-29 (27 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (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/1888994 Title: Display scale setting is not saved across reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1888994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778082] Re: Language Support Is Incomplete dialog must show package list to install
I've also observed this behavior on Kubuntu 20.04. This command appears to fix the issue: sudo apt install $(check- language-support) Reference: https://unix.stackexchange.com/questions/421066/popup- language-support-is-incomplete-what-packages-does-it-want-to-install -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778082 Title: Language Support Is Incomplete dialog must show package list to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-runtime/+bug/1778082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755305] Re: .xsession-errors filled with entries
I am encountering the same issue in 20.04. The message is repeating approximately every three seconds, resulting in log files of hundreds of gigabytes. It also makes the system log nearly useless for any other use; it is near-impossible to even open the file, and causes logrotate to hang up for hours every time it attempts to run since it attempts compression. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755305 Title: .xsession-errors filled with entries To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1755305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755305] Re: .xsession-errors filled with entries
Example of errors: Jun 1 18:27:41 europa nm-applet[2158]: Can't set a parent on widget which has a parent Jun 1 18:28:44 europa nm-applet[2158]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Jun 1 18:28:44 europa nm-applet[2158]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Jun 1 18:28:44 europa nm-applet[2158]: Can't set a parent on widget which has a parent Jun 1 18:28:44 europa nm-applet[2158]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Jun 1 18:28:44 europa nm-applet[2158]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Jun 1 18:28:44 europa nm-applet[2158]: Can't set a parent on widget which has a parent Jun 1 18:29:47 europa nm-applet[2158]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Jun 1 18:29:47 europa nm-applet[2158]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Jun 1 18:29:47 europa nm-applet[2158]: Can't set a parent on widget which has a parent Jun 1 18:29:47 europa nm-applet[2158]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Jun 1 18:29:47 europa nm-applet[2158]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755305 Title: .xsession-errors filled with entries To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1755305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835470] Re: apt-mark hold not set on kubernetes installation
Oh, additionally... Though I've never marked any package for hold until now, I'm assuming that `apt-get upgrade` would warn that it's skipping a new package that's on hold, thereby allowing me to see that a new version is available that I can chose to upgrade when I'm ready. If not, that's ok, because I can manually check available package versions if I need to. Putting a hold on the package at initial installation would be a life-saver and would have saved me many, many hours tracking down this issue -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835470 Title: apt-mark hold not set on kubernetes installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubernetes/+bug/1835470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835470] [NEW] apt-mark hold not set on kubernetes installation
Public bug reported: Not a bug in Ubuntu per se, but the Ubuntu installer behavior creates bugs in the Kubernetes cluster over time. When upgrading a minor release of Kubernetes (K8s), it's essential to run post-installation upgrade scripts on the cluster in order to bring it up-to-date with the most recent kubeadm version installed by Ubuntu. The way that it stands today, upgrading Ubuntu 18.04 LTS to keep up with patches will also automatically upgrade Kubernetes without the operator knowing that they need to take further action to bring the cluster in line with the newest minor version of K8s. If you look at the official K8s upgrade instructions for Ubuntu at https://kubernetes.io/docs/tasks /administer-cluster/kubeadm/kubeadm-upgrade-1-15/, you'll see that they are expecting a hold to be placed on the package upgrade and that the operator must release it using `apt-mark unhold kubeadm`. In my particular case, I installed K8s version 1.13.4 earlier this year on a new 18.04 LTS server and through regular patching it was automatically upgraded to 1.15.0 without my knowledge so I never upgraded the cluster to match. The result is that the pods in the cluster became unavailable at an alarming rate and my application was sending back lots of 504 Gateway Timeout errors to the browser as the result of the disconnected pod. I was able to upgrade the cluster to 1.14.0, then to 1.15.0, and that fixed the problem completely. I've now added holds for kubeadm, kubelet, and kubectl to my own installation instructions, but it would be nice if Ubuntu did this automatically on installation so that folks don't get into this pickle in the first place. Thanks. ubuntu@kubernetes-master:~$ lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 ** Affects: kubernetes (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/1835470 Title: apt-mark hold not set on kubernetes installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubernetes/+bug/1835470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805543] Re: Packaged version of iptables doesn't provide --random-fully flag.
I found this thread because I ran into a problem with a brand-new installation of Kubernetes (K8s) running in AWS that was failing a large number of browser requests being serviced by the K8s cluster. There is a ton of detail about this problem at https://tech.xing.com/a-reason-for- unexplained-connection-timeouts-on-kubernetes-docker-abd041cf7e02. To make a very long story short, we need the 1.6.2+ version of iptables on Ubuntu because it supports the --random-fully flag. Without this, any K8s cluster created on Ubuntu is pretty useless if you use local DNS to resolve cluster services by name (e.g. http://my-backend-microservice), which is what we do to support namespaces for reverse proxies (nginx). I manually built iptables 1.6.2 using the instructions at http://www.linuxfromscratch.org/blfs/view/8.2/postlfs/iptables.html and my problem appears to be solved. It would be great if the change could be backported into bionic, but at the minimum getting this into the next LTS then that would be great. If it makes any difference, iptables in Debian buster is at 1.8.2-4. They have a planned release in, oh look at that, two days :-) As for test cases, in this particular instance it's sufficient that when using the --random-fully flag to set up a NAT masquerading rule that the NF_NAT_RANGE_PROTO_RANDOM_FULLY flag is set. I can't say what the regression potential is, but since it's a minor release then I'd expect it to be minimal. The diffs are at https://www.netfilter.org/projects/iptables/files/patch- iptables-1.6.1-1.6.2.bz2 Here are some details of my installation: ubuntu@kubernetes-master:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic ubuntu@kubernetes-master:~$ uname -a Linux kubernetes-master 4.15.0-1043-aws #45-Ubuntu SMP Mon Jun 24 14:07:03 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805543 Title: Packaged version of iptables doesn't provide --random-fully flag. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1805543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15
I am running into the same situation: Running Ubuntu 18.04 in VMWare Fusion 10.1.6 on macOS 10.14.5 After I updated I received the 4.15.0-52-geeneric kernel, and the login screen no longer shows. I was able to successfully use the workaround "WaylandEnable=false" to get it to show. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832138 Title: Login screen never appears on vmwgfx using bionic kernel 4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1568459] Re: unison incompatible with older ubuntu/debian versions
Problem is still present in 18.04 The unison-all and unison-all-gtk have no real content. The only thing in them is the copyright file and a changelog file that indicates that old versions were removed. This contradicts the package description which says that it install multiple supported versions in order to sync with older systems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1568459 Title: unison incompatible with older ubuntu/debian versions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unison/+bug/1568459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803129] [NEW] Trying to move icons on the dash causes crash
Public bug reported: When trying to move an icon on the gnome dash, the cursor turns into an X and the screen goes blank. If I try again the screen goes blank and I get logged out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome (not installed) ProcVersionSignature: Ubuntu 4.15.0-38.41-lowlatency 4.15.18 Uname: Linux 4.15.0-38-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 13 10:07:49 2018 InstallationDate: Installed on 2017-10-23 (385 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: meta-gnome3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: meta-gnome3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803129 Title: Trying to move icons on the dash causes crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/1803129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798906] [NEW] jackdbus file grows to enormous sizes
Public bug reported: Looks like this has been fixed in kxstudio? https://bugs.launchpad.net/kxstudio/+bug/619014 Unfortunately still a problem in Ubuntu 18.04. The file that grows forever is ~/.log/jack/jackdbus.log. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: jackd2 1.9.12~dfsg-2 ProcVersionSignature: Ubuntu 4.15.0-36.39-lowlatency 4.15.18 Uname: Linux 4.15.0-36-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 19 18:15:03 2018 ExecutablePath: /usr/bin/jackdbus InstallationDate: Installed on 2017-10-23 (361 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: jackd2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798906 Title: jackdbus file grows to enormous sizes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1798906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785126] [NEW] package shim-signed 1.34.9.2+13-0ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: occurred during auto-update cycle ProblemType: Package DistroRelease: Ubuntu 18.04 Package: shim-signed 1.34.9.2+13-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or directory: '/proc/sys/kernel/moksbstate_disabled' ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: chromium-codecs-ffmpeg-extra:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Thu Aug 2 06:33:51 2018 DpkgHistoryLog: Start-Date: 2018-08-02 06:33:30 Commandline: /usr/bin/unattended-upgrade Upgrade: chromium-codecs-ffmpeg-extra:amd64 (67.0.3396.99-0ubuntu0.18.04.1, 68.0.3440.75-0ubuntu0.18.04.1) EFITables: Jul 22 21:16:41 opiumden kernel: efi: EFI v2.00 by American Megatrends Jul 22 21:16:41 opiumden kernel: efi: SMBIOS=0xcf63bd98 ACPI=0xcf5d5000 ACPI 2.0=0xcf5d5000 MPS=0xfcb60 Jul 22 21:16:41 opiumden kernel: secureboot: Secure boot could not be determined (mode 0) Jul 22 21:17:31 opiumden fwupd[2122]: disabling plugin because: failed to startup uefi: UEFI firmware updating not supported ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2018-06-16 (47 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: shim-signed Title: package shim-signed 1.34.9.2+13-0ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785126 Title: package shim-signed 1.34.9.2+13-0ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1785126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1391671] Re: Some Unity Launcher Icons Stop Responding in One Screen, Fine in the Other
Thank you. This is not an issue with Ubuntu 18 / Gnome 3. On Wed, Jul 11, 2018 at 4:17 PM, gf <1391...@bugs.launchpad.net> wrote: > Hello Todd, > Thank you for submitting this bug and reporting a problem with launcher > icons. You made this bug report in 2014 and there have been several > versions of Ubuntu since then. > > Could you confirm that this is no longer a problem and that we can close > the ticket? > If it is still a problem, are you still interested in finding a solution > to this bug? > If you are, could you run the following (only once): > apport-collect 1391671 > and upload the updated logs and and any other logs that are relevant for > this particular issue. > > Thank you again for helping make Ubuntu better. > G > > ** Changed in: unity (Ubuntu) >Status: New => Incomplete > > ** Changed in: unity >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1391671 > > Title: > Some Unity Launcher Icons Stop Responding in One Screen, Fine in the > Other > > Status in Unity: > Incomplete > Status in unity package in Ubuntu: > Incomplete > > Bug description: > I have two monitors displaying my desktop, and a Unity launcher in > both. I keep some applications in one screen, and some applications in > the other, and some applications (especially chat apps) I drag and > drop between screens depending on what I am working on in that moment. > > Every so often (perhaps one or two days in a workweek?), some of the > icons in the left screen (primary) launcher become unresponsive. Other > icons will work fine, but a select 3-4 of them will just not respond. > All launcher icons will work fine in the right (secondary) screen. > Today I just realized that its just my icons that correspond to apps > that I drag around that are doing this (pidgin chat windows, XChat > (irc), sometimes Thunderbird, sometimes Gnome Terminal). > > Logging out and logging back in alleviates the issue (which sucks, > major interruption of workflow). I cant seem to reproduce the issue on > my own, any combination of dragging, minimizing, opening, closing, > etc, between different screens all seem to work fine when Im > intentionally trying to recreate this bug. It usually just happens out > of no where and I cant seem to establish a pattern as to when and why. > > This is on Ubuntu 14.04 64 bit, and Ive used the same exact hardware / > peripherals for 12.04, 12.10, 13.04, and 13.10. I havent experienced > this issue before 14.04. > > ProblemType: Bug > DistroRelease: Ubuntu 14.04 > Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 > ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 > Uname: Linux 3.13.0-39-generic x86_64 > ApportVersion: 2.14.1-0ubuntu3.5 > Architecture: amd64 > CompizPlugins: No value set for `/apps/compiz-1/general/ > screen0/options/active_plugins' > CurrentDesktop: Unity > Date: Tue Nov 11 17:22:50 2014 > InstallationDate: Installed on 2014-10-09 (33 days ago) > InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 > (20140722.2) > SourcePackage: unity > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/unity/+bug/1391671/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1391671 Title: Some Unity Launcher Icons Stop Responding in One Screen, Fine in the Other To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1391671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779905] Re: 'apt-get install pulseaudio-module-jack' fails with error
Thank you, I appreciate being able to keep all the history for this bug. I've reworded the title, description, and set the status back to new. ** Summary changed: - Missing pulseaudio-module-jack files, cannot load module + 'apt-get install pulseaudio-module-jack' fails with error ** Description changed: When I try to load pulseaudio-module-jack modules, I get an error: Failure: Module initialization failed When I look in /usr/lib/pulse-8.0/modules/ there are no jack modules. - I'm on Ubuntu 16.04.04. + So I then tried to install it with `sudo apt install pulseaudio-module- + jack` after first running `sudo apt update`. The output gives me this + error: + + + Reading package lists... Done + Building dependency tree + Reading state information... Done + Package pulseaudio-module-jack is not available, but is referred to by another package. + This may mean that the package is missing, has been obsoleted, or + is only available from another source + + E: Package 'pulseaudio-module-jack' has no installation candidate ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New ** Summary changed: - 'apt-get install pulseaudio-module-jack' fails with error + 'apt install pulseaudio-module-jack' fails with error -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779905 Title: 'apt install pulseaudio-module-jack' fails with error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1779905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779905] Re: Missing pulseaudio-module-jack files, cannot load module
> That shows you are missing pulseaudio-module-jack, making this bug invalid. I don't understand what that means? > If you continue to have trouble installing the package then please log that as a new bug. Seriously? It's all part of the same problem. Is there a good reason this can't be dealt with in this bug? For now I was able to install the module using the links you gave me, but I'm still concerned that was a manual process and I'd like to fix the bug with me not being able to install it using the normal 'apt' commands and having to use 'dpkg' instead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779905 Title: Missing pulseaudio-module-jack files, cannot load module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1779905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779905] Re: Missing pulseaudio-module-jack files, cannot load module
> sudo apt update Thanks for the reminder. I always run that first and just tried it again. > You may also want to try downloading the package(s) directly: I'll try that as a stop gap. dpkg output attached. ** Attachment added: "dpkg list output" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1779905/+attachment/5160104/+files/dpkgl.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779905 Title: Missing pulseaudio-module-jack files, cannot load module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1779905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779905] Re: Missing pulseaudio-module-jack files, cannot load module
Sorry, I forget to mention the output of that: Reading package lists... Done Building dependency tree Reading state information... Done Package pulseaudio-module-jack is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'pulseaudio-module-jack' has no installation candidate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779905 Title: Missing pulseaudio-module-jack files, cannot load module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1779905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779905] Re: Missing pulseaudio-module-jack files, cannot load module
Commands I used to load modules: pactl load-module module-jack-sink pactl load-module module-jack-source -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779905 Title: Missing pulseaudio-module-jack files, cannot load module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1779905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779905] [NEW] Missing pulseaudio-module-jack files, cannot load module
Public bug reported: When I try to load pulseaudio-module-jack modules, I get an error: Failure: Module initialization failed When I look in /usr/lib/pulse-8.0/modules/ there are no jack modules. I'm on Ubuntu 16.04.04. ** Affects: pulseaudio (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/1779905 Title: Missing pulseaudio-module-jack files, cannot load module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1779905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 309578] Re: thunderbird segfaults after password prompt
This is no longer a problem. Please close this bug report. -- Todd (original reporter) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/309578 Title: thunderbird segfaults after password prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/309578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775508] [NEW] Installer crashed. Could not install GRUB boot loader on /. target
Public bug reported: Bionic Beaver 18.04 Dell T420, 96 GB RAM, 1 x Xeon 5650 @1.9 GHz ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 7 00:55:21 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) 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 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775508 Title: Installer crashed. Could not install GRUB boot loader on /. target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1775508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769406] Re: no pwsafe tray icon in Xubuntu 18.04
The PasswordSafe Github site (https://github.com/pwsafe/pwsafe) has version 1.05BETA on it, and when built from master HEAD it shows the tray icon (at least with the Ubuntu appindicators extension installed). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769406 Title: no pwsafe tray icon in Xubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pwsafe/+bug/1769406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769291] [NEW] Ubuntu Mate installer crashed
Public bug reported: Failed to write a file to root directory and subsequently ended. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 Date: Fri May 4 22:42:50 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14 ubuntu-mate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769291 Title: Ubuntu Mate installer crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1769291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638341] Re: timidity daemon using 100% CPU
This affects me on Ubuntu 16.04. I start timidity from the command line and then the system gets very slow. The output of 'top' shows timidity taking all the CPU. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638341 Title: timidity daemon using 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/timidity/+bug/1638341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1750237] Re: system will not add or remove some software. Also screen greyed out and icons were not present
*** This bug is a duplicate of bug 545790 *** https://bugs.launchpad.net/bugs/545790 Sent from my iPhone > On Feb 28, 2018, at 11:50 PM, dino99 <1750...@bugs.launchpad.net> wrote: > THANK YOU! I really appreciate your help. > *** This bug is a duplicate of bug 545790 *** >https://bugs.launchpad.net/bugs/545790 > > ** This bug has been marked a duplicate of bug 545790 > package PACKAGE failed to install/upgrade: error writing to ' output>': Success > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1750237 > > Title: > system will not add or remove some software. Also screen greyed out > and icons were not present > > Status in dpkg package in Ubuntu: > New > > Bug description: > i guess i just got greedy and added too many programs. I am very new and > don't understand how to debug on my own. System dependencies is bit out of > my league right now. Will most likely reinstall from DVD that i downloaded > and burned. I do not recall if i MD5 this or not. So that may be and issue. > The problem did not start until i added a bunch of awesome toys. > Using Ubuntu 16.04.3 LTS Release 16.04 > > sorry i can't give more data than that > > ProblemType: Package > DistroRelease: Ubuntu 16.04 > Package: libcups2:amd64 2.1.3-4ubuntu0.3 > ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-lowlatency 4.13.13 > Uname: Linux 4.13.0-32-lowlatency x86_64 > ApportVersion: 2.20.1-0ubuntu2.15 > AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 > Architecture: amd64 > CrashReports: > 600:0:117:394601:2018-02-18 06:03:01.180194139 -0600:2018-02-18 > 06:03:02.180194139 -0600:/var/crash/texlive-latex-base.0.crash > 600:0:117:387079:2018-02-18 05:58:13.489199638 -0600:2018-02-18 > 05:58:14.489199638 -0600:/var/crash/libcups2:amd64.0.crash > 640:1000:117:98508:2018-02-16 06:17:26.441312789 -0600:2018-02-16 > 06:17:27.441312789 -0600:/var/crash/_usr_bin_gnome-software.1000.crash > CupsErrorLog: > W [18/Feb/2018:05:56:07 -0600] CreateProfile failed: > org.freedesktop.ColorManager.AlreadyExists:profile id > \'HP-ENVY-5530-series-Gray..\' already exists > W [18/Feb/2018:05:56:07 -0600] CreateProfile failed: > org.freedesktop.ColorManager.AlreadyExists:profile id > \'HP-ENVY-5530-series-RGB..\' already exists > Date: Sun Feb 18 05:58:13 2018 > DuplicateSignature: > package:libcups2:amd64:2.1.3-4ubuntu0.3 > Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... > dpkg: error processing package libcups2:amd64 (--configure): >package libcups2:amd64 is already installed and configured > ErrorMessage: package libcups2:amd64 is already installed and configured > InstallationDate: Installed on 2018-02-16 (2 days ago) > InstallationMedia: Ubuntu-Studio 16.04.3 LTS "Xenial Xerus" - Release amd64 > (20170801) > Lpstat: device for HP-ENVY-5530-series: > hp:/net/ENVY_5530_series?zc=HP3464A9E99E09 > MachineType: Sony Corporation VGN-NR220E > Papersize: letter > PccardctlIdent: > Socket 0: > no product info available > PccardctlStatus: > Socket 0: > no card > PpdFiles: HP-ENVY-5530-series: HP Envy 5530 Series, hpcups 3.16.3 > ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-lowlatency > root=UUID=1b7ff9e9-9345-4b33-9dae-9045cd67aa0a ro quiet splash vt.handoff=7 > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-lowlatency > root=UUID=1b7ff9e9-9345-4b33-9dae-9045cd67aa0a ro quiet splash vt.handoff=7 > RelatedPackageVersions: > dpkg 1.18.4ubuntu1.3 > apt 1.2.25 > SourcePackage: dpkg > Title: package libcups2:amd64 2.1.3-4ubuntu0.3 failed to install/upgrade: > package libcups2:amd64 is already installed and configured > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 10/23/2007 > dmi.bios.vendor: Phoenix Technologies LTD > dmi.bios.version: R1101J9 > dmi.board.asset.tag: N/A > dmi.board.name: VAIO > dmi.board.vendor: Sony Corporation > dmi.board.version: N/A > dmi.chassis.asset.tag: N/A > dmi.chassis.type: 10 > dmi.chassis.vendor: Sony Corporation > dmi.chassis.version: N/A > dmi.modalias: > dmi:bvnPhoenixTechnologiesLTD:bvrR1101J9:bd10/23/2007:svnSonyCorporation:pnVGN-NR220E:pvrC3LQLBBY:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: > dmi.product.family: N/A > dmi.product.name: VGN-NR220E > dmi.product.version: C3LQLBBY > dmi.sys.vendor: Sony Corporation > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1750237/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750237 Title: system will not add or remove some software. Also screen greyed out and icons were not present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1750237/+subscriptions -- ubuntu-bugs mailing list
Re: [Bug 1750237] Re: system will not add or remove some software. Also screen greyed out and icons were not present
Sir, wow I wasn’t expecting a real reply. After all I just downloaded a free iso. Well it could be rooted in the fact that I have 3 distress on this system. Pun intended. : Sda1 kali, sda2 ubuntustudio, sda3 linuxmint 17.1 each time I installed them I set them up at /. I don’t yet know how to move manually where each should be under GRUB 2.02. Maybe that will help. Feel free to txt for faster response 817-219-3667 I’m daniEL Sent from my iPhone > On Feb 18, 2018, at 5:10 PM, Gustavo Silva <1750...@bugs.launchpad.net> wrote: > > Can you add more details regarding what you were doing before all this > happened? Judging by some of the logs, it seems you may have corrupted > key packages in the distribution but to be sure of that, I need to know > what commands you ran. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1750237 > > Title: > system will not add or remove some software. Also screen greyed out > and icons were not present > > Status in dpkg package in Ubuntu: > New > > Bug description: > i guess i just got greedy and added too many programs. I am very new and > don't understand how to debug on my own. System dependencies is bit out of > my league right now. Will most likely reinstall from DVD that i downloaded > and burned. I do not recall if i MD5 this or not. So that may be and issue. > The problem did not start until i added a bunch of awesome toys. > Using Ubuntu 16.04.3 LTS Release 16.04 > > sorry i can't give more data than that > > ProblemType: Package > DistroRelease: Ubuntu 16.04 > Package: libcups2:amd64 2.1.3-4ubuntu0.3 > ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-lowlatency 4.13.13 > Uname: Linux 4.13.0-32-lowlatency x86_64 > ApportVersion: 2.20.1-0ubuntu2.15 > AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 > Architecture: amd64 > CrashReports: > 600:0:117:394601:2018-02-18 06:03:01.180194139 -0600:2018-02-18 > 06:03:02.180194139 -0600:/var/crash/texlive-latex-base.0.crash > 600:0:117:387079:2018-02-18 05:58:13.489199638 -0600:2018-02-18 > 05:58:14.489199638 -0600:/var/crash/libcups2:amd64.0.crash > 640:1000:117:98508:2018-02-16 06:17:26.441312789 -0600:2018-02-16 > 06:17:27.441312789 -0600:/var/crash/_usr_bin_gnome-software.1000.crash > CupsErrorLog: > W [18/Feb/2018:05:56:07 -0600] CreateProfile failed: > org.freedesktop.ColorManager.AlreadyExists:profile id > \'HP-ENVY-5530-series-Gray..\' already exists > W [18/Feb/2018:05:56:07 -0600] CreateProfile failed: > org.freedesktop.ColorManager.AlreadyExists:profile id > \'HP-ENVY-5530-series-RGB..\' already exists > Date: Sun Feb 18 05:58:13 2018 > DuplicateSignature: > package:libcups2:amd64:2.1.3-4ubuntu0.3 > Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... > dpkg: error processing package libcups2:amd64 (--configure): >package libcups2:amd64 is already installed and configured > ErrorMessage: package libcups2:amd64 is already installed and configured > InstallationDate: Installed on 2018-02-16 (2 days ago) > InstallationMedia: Ubuntu-Studio 16.04.3 LTS "Xenial Xerus" - Release amd64 > (20170801) > Lpstat: device for HP-ENVY-5530-series: > hp:/net/ENVY_5530_series?zc=HP3464A9E99E09 > MachineType: Sony Corporation VGN-NR220E > Papersize: letter > PccardctlIdent: > Socket 0: > no product info available > PccardctlStatus: > Socket 0: > no card > PpdFiles: HP-ENVY-5530-series: HP Envy 5530 Series, hpcups 3.16.3 > ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-lowlatency > root=UUID=1b7ff9e9-9345-4b33-9dae-9045cd67aa0a ro quiet splash vt.handoff=7 > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-lowlatency > root=UUID=1b7ff9e9-9345-4b33-9dae-9045cd67aa0a ro quiet splash vt.handoff=7 > RelatedPackageVersions: > dpkg 1.18.4ubuntu1.3 > apt 1.2.25 > SourcePackage: dpkg > Title: package libcups2:amd64 2.1.3-4ubuntu0.3 failed to install/upgrade: > package libcups2:amd64 is already installed and configured > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 10/23/2007 > dmi.bios.vendor: Phoenix Technologies LTD > dmi.bios.version: R1101J9 > dmi.board.asset.tag: N/A > dmi.board.name: VAIO > dmi.board.vendor: Sony Corporation > dmi.board.version: N/A > dmi.chassis.asset.tag: N/A > dmi.chassis.type: 10 > dmi.chassis.vendor: Sony Corporation > dmi.chassis.version: N/A > dmi.modalias: > dmi:bvnPhoenixTechnologiesLTD:bvrR1101J9:bd10/23/2007:svnSonyCorporation:pnVGN-NR220E:pvrC3LQLBBY:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: > dmi.product.family: N/A > dmi.product.name: VGN-NR220E > dmi.product.version: C3LQLBBY > dmi.sys.vendor: Sony Corporation > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1750237/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to
[Bug 1750237] Re: system will not add or remove some software. Also screen greyed out and icons were not present
Hope this helps make Ubuntu Studio a more functional tool for other users -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750237 Title: system will not add or remove some software. Also screen greyed out and icons were not present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1750237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750237] [NEW] system will not add or remove some software. Also screen greyed out and icons were not present
Public bug reported: i guess i just got greedy and added too many programs. I am very new and don't understand how to debug on my own. System dependencies is bit out of my league right now. Will most likely reinstall from DVD that i downloaded and burned. I do not recall if i MD5 this or not. So that may be and issue. The problem did not start until i added a bunch of awesome toys. Using Ubuntu 16.04.3 LTS Release 16.04 sorry i can't give more data than that ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libcups2:amd64 2.1.3-4ubuntu0.3 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-lowlatency 4.13.13 Uname: Linux 4.13.0-32-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.15 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 CrashReports: 600:0:117:394601:2018-02-18 06:03:01.180194139 -0600:2018-02-18 06:03:02.180194139 -0600:/var/crash/texlive-latex-base.0.crash 600:0:117:387079:2018-02-18 05:58:13.489199638 -0600:2018-02-18 05:58:14.489199638 -0600:/var/crash/libcups2:amd64.0.crash 640:1000:117:98508:2018-02-16 06:17:26.441312789 -0600:2018-02-16 06:17:27.441312789 -0600:/var/crash/_usr_bin_gnome-software.1000.crash CupsErrorLog: W [18/Feb/2018:05:56:07 -0600] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP-ENVY-5530-series-Gray..\' already exists W [18/Feb/2018:05:56:07 -0600] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP-ENVY-5530-series-RGB..\' already exists Date: Sun Feb 18 05:58:13 2018 DuplicateSignature: package:libcups2:amd64:2.1.3-4ubuntu0.3 Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... dpkg: error processing package libcups2:amd64 (--configure): package libcups2:amd64 is already installed and configured ErrorMessage: package libcups2:amd64 is already installed and configured InstallationDate: Installed on 2018-02-16 (2 days ago) InstallationMedia: Ubuntu-Studio 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lpstat: device for HP-ENVY-5530-series: hp:/net/ENVY_5530_series?zc=HP3464A9E99E09 MachineType: Sony Corporation VGN-NR220E Papersize: letter PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card PpdFiles: HP-ENVY-5530-series: HP Envy 5530 Series, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-lowlatency root=UUID=1b7ff9e9-9345-4b33-9dae-9045cd67aa0a ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-lowlatency root=UUID=1b7ff9e9-9345-4b33-9dae-9045cd67aa0a ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: dpkg Title: package libcups2:amd64 2.1.3-4ubuntu0.3 failed to install/upgrade: package libcups2:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R1101J9 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR1101J9:bd10/23/2007:svnSonyCorporation:pnVGN-NR220E:pvrC3LQLBBY:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: N/A dmi.product.name: VGN-NR220E dmi.product.version: C3LQLBBY dmi.sys.vendor: Sony Corporation ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750237 Title: system will not add or remove some software. Also screen greyed out and icons were not present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1750237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750045] [NEW] package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account
Public bug reported: Target Sources (main/source/Sources) is configured multiple times in /etc/apt/sources.list:45 and /etc/apt/sources.list:46 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: kaccounts-providers (not installed) ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Feb 16 14:32:25 2018 DuplicateSignature: package:kaccounts-providers:(not installed) Unpacking kaccounts-providers (4:15.12.3-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/kaccounts-providers_4%3a15.12.3-0ubuntu1_amd64.deb (--unpack): trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 ErrorMessage: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 InstallationDate: Installed on 2017-06-05 (256 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: kaccounts-providers Title: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kaccounts-providers (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750045 Title: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit- options.d/www.facebook.com.conf', which is also in package account- plugin-facebook 0.12+16.04.20160126-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kaccounts-providers/+bug/1750045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743503] [NEW] No wayland session option
Public bug reported: Per the release notes, Wayland is now the default display server in Ubuntu 17.10. Exciting. https://wiki.ubuntu.com/ArtfulAardvark/ReleaseNotes I don't appear to be running Wayland. Boring. todd@todd-ab28d3:~$ loginctl SESSIONUID USER SEAT TTY c2121 gdm seat0/dev/tty1 3 1000 todd seat0/dev/tty2 2 sessions listed. todd@todd-ab28d3:~$ loginctl show-session 3 -p Type Type=x11 This is a clean install with no proprietary graphics drivers. todd@todd-ab28d3:~$ lspci | grep -i amd 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Fiji [Radeon R9 FURY / NANO Series] (rev ca) 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Fiji HDMI/DP Audio [Radeon R9 Nano / FURY/FURY X] I've attached the full journalctl log in case there's anything useful in there. No wayland hits anyway. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-session 3.26.1-0ubuntu6 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 15 23:35:06 2018 InstallationDate: Installed on 2017-12-05 (42 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743503 Title: No wayland session option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1743503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726262] Re: 17.10 - flickering overlay patterns in gnome-terminal
This is happening to me too. It's HUGELY distracting when trying to use 2, 3, or more terminal windows. I have 3x U2711 monitors hooked up via display port to a R9 Fury, so hardware doesn't seem to be a commonality. Thanks for the Gnome Profile Terminal transparency workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726262 Title: 17.10 - flickering overlay patterns in gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1726262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621179] Re: weather can not get data ( http://weather.noaa.gov has been discontinued)
This worked amazing. Thank you from a beginner (used it on my raspberry pi zero)! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621179 Title: weather can not get data ( http://weather.noaa.gov has been discontinued) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/weather-util/+bug/1621179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718783] [NEW] package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported:
Description:Ubuntu 16.04.3 LTS
Release:16.04
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
.proc.sys.kernel.moksbstate_disabled: 0
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Thu Sep 21 15:47:47 2017
EFIBootMgr:
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002,
Boot* Windows Boot Manager
HD(1,GPT,72eff785-cc1b-4c80-b9c8-0e165ab9d663,0x800,0xfa000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....
Boot0002* ubuntu
HD(1,GPT,72eff785-cc1b-4c80-b9c8-0e165ab9d663,0x800,0xfa000)/File(\EFI\ubuntu\shimx64.efi)
EFITables:
Sep 21 17:09:04 tc-XPS-15-9560 kernel: efi: EFI v2.40 by American Megatrends
Sep 21 17:09:04 tc-XPS-15-9560 kernel: efi: ACPI=0x78821000 ACPI
2.0=0x78821000 SMBIOS=0xf SMBIOS 3.0=0xf0020 ESRT=0x792d2018
MEMATTR=0x75dfd018
Sep 21 17:09:04 tc-XPS-15-9560 kernel: esrt: Reserving ESRT space from
0x792d2018 to 0x792d2050.
Sep 21 17:09:04 tc-XPS-15-9560 kernel: Secure boot enabled
ErrorMessage: subprocess installed post-installation script returned error exit
status 1
InstallationDate: Installed on 2017-09-21 (0 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.2
apt 1.2.24
SecureBoot: 6 0 0 0 1
SourcePackage: shim-signed
Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed
to install/upgrade: subprocess installed post-installation script returned
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: shim-signed (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-package xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718783
Title:
package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
failed to install/upgrade: subprocess installed post-installation
script returned error exit status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1718783/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711375] [NEW] Crash occurred during "apt upgrade" w/ 500+ packages updating
Public bug reported: Occurred as part of the upgrade, briefly saw 'upstart' mentioned in details. This is of little concern to me; I am confident I can fix if necessary though currently I use docker container(s) for my mysql db needs. However, may provide useful info to you. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: mysql-server-5.7 5.7.19-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Wed Aug 16 19:18:25 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-06-06 (1898 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqld_safe_syslog.cnf: [mysqld_safe] syslog MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf: [mysqld_safe] syslog MySQLVarLibDirListing: ['performance_schema', 'ibdata1', 'ib_logfile1', 'auto.cnf', 'debian-5.7.flag', 'debian-5.5.flag', 'sys', 'ib_buffer_pool', 'test', 'ib_logfile0', 'bbf', 'mysql', 'mysql_upgrade_info'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=5980d7dd-a309-45b0-8f51-f8a4638d98b4 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: mysql-5.7 Title: package mysql-server-5.7 5.7.19-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-11-15 (274 days ago) modified.conffile..etc.logrotate.d.mysql-server: [modified] mtime.conffile..etc.logrotate.d.mysql-server: 2017-06-24T12:54:08.791484 upstart.mysql.override: manual ** Affects: mysql-5.7 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711375 Title: Crash occurred during "apt upgrade" w/ 500+ packages updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1711375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675386] Re: all network devices aren't added to instance profile
** Description changed:
RELEASE: nova-compute-lxd 13.3.0-0ubuntu1
DESCRIPTION:
In config.py the network_devices object should be returned after the
'for vifaddr in network_info:' loop to ensure the network_devices object
includes all network devices.
CURRENT CODE (annotated area of interest with ):
- def create_network(self, instance_name, instance, network_info):
- """Create the LXD container network on the host
+ def create_network(self, instance_name, instance, network_info):
+ """Create the LXD container network on the host
- :param instance_name: nova instance name
- :param instance: nova instance object
- :param network_info: instance network configuration object
- :return:network configuration dictionary
- """
- LOG.debug('create_network called for instance', instance=instance)
- try:
- network_devices = {}
- if not network_info:
- return
- for vifaddr in network_info:
- cfg = self.vif_driver.get_config(instance, vifaddr)
- key = str(cfg['bridge'])
- network_devices[key] = {'nictype': 'bridged', 'hwaddr':
str(cfg['mac_address']), 'parent': key, 'type': 'nic'}
- host_device = self.vif_driver.get_vif_devname(vifaddr)
- if host_device:
- network_devices[key]['host_name'] = host_device
+ :param instance_name: nova instance name
+ :param instance: nova instance object
+ :param network_info: instance network configuration object
+ :return:network configuration dictionary
+ """
+ LOG.debug('create_network called for instance', instance=instance)
+ try:
+ network_devices = {}
+ if not network_info:
+ return
+ for vifaddr in network_info:
+ cfg = self.vif_driver.get_config(instance, vifaddr)
+ key = str(cfg['bridge'])
+ network_devices[key] = {'nictype': 'bridged', 'hwaddr':
str(cfg['mac_address']), 'parent': key, 'type': 'nic'}
+ host_device = self.vif_driver.get_vif_devname(vifaddr)
+ if host_device:
+ network_devices[key]['host_name'] = host_device
return network_devices
- except Exception as ex:
- with excutils.save_and_reraise_exception():
- LOG.error(
- _LE('Fail to configure network for %(instance)s: %(ex)s'),
- {'instance': instance_name, 'ex': ex}, instance=instance)
+ except Exception as ex:
+ with excutils.save_and_reraise_exception():
+ LOG.error(
+ _LE('Fail to configure network for %(instance)s: %(ex)s'),
+ {'instance': instance_name, 'ex': ex}, instance=instance)
PROPOSED CHANGE (annotated area of interest with ):
- def create_network(self, instance_name, instance, network_info):
- """Create the LXD container network on the host
+ def create_network(self, instance_name, instance, network_info):
+ """Create the LXD container network on the host
- :param instance_name: nova instance name
- :param instance: nova instance object
- :param network_info: instance network configuration object
- :return:network configuration dictionary
- """
- LOG.debug('create_network called for instance', instance=instance)
- try:
- network_devices = {}
- if not network_info:
- return
- for vifaddr in network_info:
- cfg = self.vif_driver.get_config(instance, vifaddr)
- key = str(cfg['bridge'])
- network_devices[key] = {'nictype': 'bridged', 'hwaddr':
str(cfg['mac_address']), 'parent': key, 'type': 'nic'}
- host_device = self.vif_driver.get_vif_devname(vifaddr)
- if host_device:
- network_devices[key]['host_name'] = host_device
- except Exception as ex:
- with excutils.save_and_reraise_exception():
- LOG.error(
- _LE('Fail to configure network for %(instance)s: %(ex)s'),
- {'instance': instance_name, 'ex': ex}, instance=instance)
- return network_devices
+ :param instance_name: nova instance name
+ :param instance: nova instance object
+ :param network_info: instance network configuration object
+ :return:network configuration dictionary
+ """
+ LOG.debug('create_network called for instance', instance=instance)
+ try:
+ network_devices = {}
+ if not network_info:
+ return
+ for vifaddr in network_info:
+ cfg =
[Bug 1675386] [NEW] all network devices aren't added to instance profile
Public bug reported:
RELEASE: nova-compute-lxd 13.3.0-0ubuntu1
DESCRIPTION:
In config.py the network_devices object should be returned after the
'for vifaddr in network_info:' loop to ensure the network_devices object
includes all network devices.
CURRENT CODE (annotated area of interest with ):
def create_network(self, instance_name, instance, network_info):
"""Create the LXD container network on the host
:param instance_name: nova instance name
:param instance: nova instance object
:param network_info: instance network configuration object
:return:network configuration dictionary
"""
LOG.debug('create_network called for instance', instance=instance)
try:
network_devices = {}
if not network_info:
return
for vifaddr in network_info:
cfg = self.vif_driver.get_config(instance, vifaddr)
key = str(cfg['bridge'])
network_devices[key] = {'nictype': 'bridged', 'hwaddr':
str(cfg['mac_address']), 'parent': key, 'type': 'nic'}
host_device = self.vif_driver.get_vif_devname(vifaddr)
if host_device:
network_devices[key]['host_name'] = host_device
return network_devices
except Exception as ex:
with excutils.save_and_reraise_exception():
LOG.error(
_LE('Fail to configure network for %(instance)s: %(ex)s'),
{'instance': instance_name, 'ex': ex}, instance=instance)
PROPOSED CHANGE (annotated area of interest with ):
def create_network(self, instance_name, instance, network_info):
"""Create the LXD container network on the host
:param instance_name: nova instance name
:param instance: nova instance object
:param network_info: instance network configuration object
:return:network configuration dictionary
"""
LOG.debug('create_network called for instance', instance=instance)
try:
network_devices = {}
if not network_info:
return
for vifaddr in network_info:
cfg = self.vif_driver.get_config(instance, vifaddr)
key = str(cfg['bridge'])
network_devices[key] = {'nictype': 'bridged', 'hwaddr':
str(cfg['mac_address']), 'parent': key, 'type': 'nic'}
host_device = self.vif_driver.get_vif_devname(vifaddr)
if host_device:
network_devices[key]['host_name'] = host_device
except Exception as ex:
with excutils.save_and_reraise_exception():
LOG.error(
_LE('Fail to configure network for %(instance)s: %(ex)s'),
{'instance': instance_name, 'ex': ex}, instance=instance)
return network_devices
** Affects: nova-lxd (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/1675386
Title:
all network devices aren't added to instance profile
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nova-lxd/+bug/1675386/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
