[Touch-packages] [Bug 1713803] Re: replacement of resolvconf with systemd needs integration
Does dhcpcd5 version 9.4.1-0.1 solve the issue for you?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1713803
Title:
replacement of resolvconf with systemd needs integration
Status in android-androresolvd package in Ubuntu:
Triaged
Status in avahi package in Ubuntu:
Triaged
Status in bind9 package in Ubuntu:
Triaged
Status in cloud-init package in Ubuntu:
Invalid
Status in cloud-initramfs-tools package in Ubuntu:
Invalid
Status in dhcpcd5 package in Ubuntu:
Confirmed
Status in dibbler package in Ubuntu:
Won't Fix
Status in dnscrypt-proxy package in Ubuntu:
Confirmed
Status in dnsmasq package in Ubuntu:
Invalid
Status in dnssec-trigger package in Ubuntu:
Invalid
Status in fetchmail package in Ubuntu:
Confirmed
Status in freedombox-setup package in Ubuntu:
Confirmed
Status in initramfs-tools package in Ubuntu:
Fix Released
Status in isc-dhcp package in Ubuntu:
Fix Released
Status in ndisc6 package in Ubuntu:
Fix Released
Status in netscript-2.4 package in Ubuntu:
Won't Fix
Status in open-iscsi package in Ubuntu:
Triaged
Status in openvpn package in Ubuntu:
Confirmed
Status in postfix package in Ubuntu:
Invalid
Status in pppconfig package in Ubuntu:
Confirmed
Status in pump package in Ubuntu:
Confirmed
Status in resolvconf package in Ubuntu:
Invalid
Status in sendmail package in Ubuntu:
Invalid
Status in squid3 package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Invalid
Status in unbound package in Ubuntu:
Triaged
Status in vpnc package in Ubuntu:
Invalid
Status in vpnc-scripts package in Ubuntu:
Invalid
Status in whereami package in Ubuntu:
Triaged
Bug description:
There is a plan to remove resolvconf from the Ubuntu Server image.
resolvconf integrated with other parts of the system in 2 ways:
* hooks invoked on change (/etc/resolvconf/update.d/)
* resolvconf tool (invoked with -a and -d or -u)
Packages which install files into /etc/resolvconf/update.d are:
- dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
caching path).
- resolvconf: This probably isn't necessary in systemd-resolved path.
- unbound: This is another "validating, recursive, caching DNS resolver".
The list of Depends/Suggests/Recommends on resolvconf.
# for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;;
Recommends:*) r=recommends;; esac; echo "$r $src"; done | sort -u
depends android-androresolvd
recommends avahi
recommends dhcpcd5
recommends dibbler
recommends ndisc6
recommends whereami
suggests bind9
suggests dnscrypt-proxy
suggests dnsmasq
suggests dnssec-trigger
suggests fetchmail
suggests freedombox-setup
suggests isc-dhcp
suggests netscript-2.4
suggests openvpn
suggests postfix
suggests pppconfig
suggests pump
suggests resolvconf
suggests sendmail
suggests squid3
suggests vpnc
suggests vpnc-scripts
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu9
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
Date: Tue Aug 29 18:53:50 2017
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.vendor: Intel Corporation
Related bugs:
* bug 1698181: Switch to netplan renderer in Artful
* bug 1714308: dns does not work in initramfs after configure_networking
* bug 1717983 replacement of isc-dhcp-client with with systemd-networkd for
dhclient needs integration
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-androresolvd/+bug/1713803/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547589] Re: rtkit-daemon flooding syslog
An easy way to solve this problem is to use the LogLevelMax systemd property: 1. As root, run `systemctl edit rtkit-daemon` to create a new droppin for this service. 2. Add this to the new file: [Service] LogLevelMax=warning 3. Restart the service: `systemctl restart rtkit-daemon` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1547589 Title: rtkit-daemon flooding syslog Status in Rtkit: New Status in rtkit package in Ubuntu: Confirmed Status in rtkit package in Debian: Confirmed Bug description: rtkit is flooding syslog with the following: Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. This may be related to but #1547585 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: rtkit 0.11-4 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 19 11:42:58 2016 InstallationDate: Installed on 2016-02-11 (7 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) SourcePackage: rtkit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/rtkit/+bug/1547589/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895762] [NEW] PH-B-500 Headphone makes bluetooth loop
You have been subscribed to a public bug: Hi there, I am using Ubuntu 18.04.4 LTS(Brazilian Portuguese, so, sorry if I translated wrong some label) in a Dell Inspiron 15 series 3000 and I am having some Bluetooth problems. I always suffer to synchronize my Cadenza PH-B Bluetooth Headphone. It Shows as PH-B-500 at the bluetooth devices list What happens is: 1. I turn on the headphone 2. I go to Settings → Bluetooth 3. The Notebook entire bluetooth enters a shutdown reinitialize loop 4. It only stops when I turn off the headphone But if I: 1. Keep the headphone off 2. go to Settings → Bluetooth 3. Click on the PH-B-500 on the list 4. Turn the headphone on and at the same time click on Conection at the PH-B-500 Bluetooth window it usually starts working fine. The headphone works perfectly on my Android cell phone so I don’t believe it is broken. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: bluetooth bot-comment headphone ph-b-500 -- PH-B-500 Headphone makes bluetooth loop https://bugs.launchpad.net/bugs/1895762 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895762] Re: PH-B-500 Headphone makes bluetooth loop
** Summary changed: - PH-B-500 Headphone makes bluetooh loop + PH-B-500 Headphone makes bluetooth loop ** Package changed: ubuntu => bluez (Ubuntu) ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1895762 Title: PH-B-500 Headphone makes bluetooth loop Status in bluez package in Ubuntu: New Bug description: Hi there, I am using Ubuntu 18.04.4 LTS(Brazilian Portuguese, so, sorry if I translated wrong some label) in a Dell Inspiron 15 series 3000 and I am having some Bluetooth problems. I always suffer to synchronize my Cadenza PH-B Bluetooth Headphone. It Shows as PH-B-500 at the bluetooth devices list What happens is: 1. I turn on the headphone 2. I go to Settings → Bluetooth 3. The Notebook entire bluetooth enters a shutdown reinitialize loop 4. It only stops when I turn off the headphone But if I: 1. Keep the headphone off 2. go to Settings → Bluetooth 3. Click on the PH-B-500 on the list 4. Turn the headphone on and at the same time click on Conection at the PH-B-500 Bluetooth window it usually starts working fine. The headphone works perfectly on my Android cell phone so I don’t believe it is broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1895762/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1976155] [NEW] [HP Spectre x360 Convertible 13-aw2xxx, Intel Tigerlake HDMI, Digital Out, HDMI] No sound at all
Public bug reported: I have tried everything I could find on the web to try and fix this. The sound input and outputs do not work on my machine. The only way I can hear sounds is if I use a bluetooth headset and in that case too the mic/input doesn't work so I cannot attend meetings and calls. The internal speaker nor the 3.5mm headphones jack work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gitarlvr53 1409 F pulseaudio /dev/snd/pcmC0D0p: gitarlvr53 1409 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 28 08:17:26 2022 InstallationDate: Installed on 2022-05-18 (10 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofsoundwire failed Symptom_Card: sof-soundwire - sof-soundwire Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gitarlvr53 1409 F pulseaudio /dev/snd/pcmC0D0p: gitarlvr53 1409 F...m pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [HP Spectre x360 Convertible 13-aw2xxx, Intel Tigerlake HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2021 dmi.bios.release: 15.15 dmi.bios.vendor: AMI dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8709 dmi.board.vendor: HP dmi.board.version: 31.32 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 31.32 dmi.modalias: dmi:bvnAMI:bvrF.15:bd12/20/2021:br15.15:efr31.32:svnHP:pnHPSpectrex360Convertible13-aw2xxx:pvr:rvnHP:rn8709:rvr31.32:cvnHP:ct31:cvrChassisVersion:sku2D9H6PA#ACJ: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-aw2xxx dmi.product.sku: 2D9H6PA#ACJ dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-26T08:42:52.633727 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1976155 Title: [HP Spectre x360 Convertible 13-aw2xxx, Intel Tigerlake HDMI, Digital Out, HDMI] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: I have tried everything I could find on the web to try and fix this. The sound input and outputs do not work on my machine. The only way I can hear sounds is if I use a bluetooth headset and in that case too the mic/input doesn't work so I cannot attend meetings and calls. The internal speaker nor the 3.5mm headphones jack work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gitarlvr53 1409 F pulseaudio /dev/snd/pcmC0D0p: gitarlvr53 1409 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 28 08:17:26 2022 InstallationDate: Installed on 2022-05-18 (10 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofsoundwire failed Symptom_Card: sof-soundwire - sof-soundwire Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gitarlvr53 1409 F pulseaudio /dev/snd/pcmC0D0p: gitarlvr53 1409 F...m pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [HP Spectre x360 Convertible 13-aw2xxx, Intel Tigerlake HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2021 dmi.bios.release: 15.15 dmi.bios.vendor: AMI dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8709 dmi.board.vendor: HP dmi.board.version: 31.32 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 31.32 dmi.modalias:
[Touch-packages] [Bug 1976160] Re: Sound card not detected (Dummy Output) after update to kernel 4.15.0-177-generic or 4.15.0.180-generic
This is related to linux-image-4.15.0-177-generic, but I cannot find that package as an option. ** Package changed: alsa-driver (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1976160 Title: Sound card not detected (Dummy Output) after update to kernel 4.15.0-177-generic or 4.15.0.180-generic Status in Ubuntu: New Bug description: Regular update including new kernel images. After reboot, sound was not working and only the dummy output is shown. Description: Ubuntu 18.04.6 LTS Release: 18.04 Package:linux-image-4.15.0-177-generic (also happens with 180-generic Expected: Sound to work, mic to work, sound card recognised in settings. What happened instead: Dummy sound only available card, sound does not work, mic does not work Tried: Restarting pulse audio, grepping lsmod for a sound card (nothing listed) Workaround: Everything works fine if I boot into 4.15.0-176-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1976160/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home
** Changed in: lvm2 (Ubuntu) Assignee: Canonical Foundations Team (canonical-foundations) => (unassigned) ** Changed in: ubuntu-z-systems Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1874381 Title: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home Status in Ubuntu on IBM z Systems: Confirmed Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Focal: Confirmed Bug description: After upgrading an LPAR configured with LVM from 18.04 to 20.04 /home is no longer mounted. During boot the console shows Timed out waiting for device /dev/mapper/s5lp8--vg-home Please see the attached dist-upgrade logs and console output for more detail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1971242] [NEW] printing PDF appears always grey, no color
You have been subscribed to a public bug: After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF document. The print appears always b/w regardless color printing was enabled or not. Printing from LibreOffice produces a color print. This behavior (bug) is reproducible on three upgraded machines. It would be nice to have color print back again. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Affects: atril (Ubuntu) Importance: Undecided Status: New ** Affects: okular (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- printing PDF appears always grey, no color https://bugs.launchpad.net/bugs/1971242 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968845] Re: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot
*** This bug is a duplicate of bug 1969162 *** https://bugs.launchpad.net/bugs/1969162 @Brian Murray: Yes, today i ran into this issue on 2 servers. The install stalled after "A reboot is required to replace the running dbus-daemon.", and then the installer resumed after 10 minutes. The first server i upgraded I've been caught by the misleading "Please reboot the system when convenient." and just rebooted after a few minutes because the installer was doing nothing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1968845 Title: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot Status in dbus package in Ubuntu: Incomplete Bug description: Upgrading on a virtual machine from 20.04 to 22.04. I have had this happen twice now, I got one upgrade done without this bug. Basically the package installation stops at dbus package asking for a reboot as it was unable to upgrade as dbus-daemon was running. And rebooting at this stage obviously will cause a non-functioning system. Added a screenshot of the upgrade window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1968845/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1971242] Re: printing PDF appears always grey, no color
** Package changed: ubuntu => cups (Ubuntu) ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1971242 Title: printing PDF appears always grey, no color Status in atril package in Ubuntu: New Status in cups package in Ubuntu: New Status in okular package in Ubuntu: New Bug description: After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF document. The print appears always b/w regardless color printing was enabled or not. Printing from LibreOffice produces a color print. This behavior (bug) is reproducible on three upgraded machines. It would be nice to have color print back again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atril/+bug/1971242/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968625] Re: package vim-common 2:8.1.2269-1ubuntu5.7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura
"package is in a very bad inconsistent state" suggests a bad download and not an Ubuntu bug. If this is still an issue then: sudo apt clean sudo apt update sudo apt install vim-common and may be sudo -f install should fix the problem. ** Changed in: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1968625 Title: package vim-common 2:8.1.2269-1ubuntu5.7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in vim package in Ubuntu: Incomplete Bug description: I don't know. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: vim-common 2:8.1.2269-1ubuntu5.7 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 11 14:08:22 2022 DuplicateSignature: package:vim-common:2:8.1.2269-1ubuntu5.7 Setting up libwbclient0:amd64 (2:4.13.17~dfsg-0ubuntu0.21.04.2) ... dpkg: error processing package vim-common (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2021-12-28 (104 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) 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: vim Title: package vim-common 2:8.1.2269-1ubuntu5.7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1968625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1976160] [NEW] Sound card not detected (Dummy Output) after update to kernel 4.15.0-177-generic or 4.15.0.180-generic
Public bug reported: Regular update including new kernel images. After reboot, sound was not working and only the dummy output is shown. Description:Ubuntu 18.04.6 LTS Release:18.04 Package:linux-image-4.15.0-177-generic (also happens with 180-generic Expected: Sound to work, mic to work, sound card recognised in settings. What happened instead: Dummy sound only available card, sound does not work, mic does not work Tried: Restarting pulse audio, grepping lsmod for a sound card (nothing listed) Workaround: Everything works fine if I boot into 4.15.0-176-generic ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1976160 Title: Sound card not detected (Dummy Output) after update to kernel 4.15.0-177-generic or 4.15.0.180-generic Status in alsa-driver package in Ubuntu: New Bug description: Regular update including new kernel images. After reboot, sound was not working and only the dummy output is shown. Description: Ubuntu 18.04.6 LTS Release: 18.04 Package:linux-image-4.15.0-177-generic (also happens with 180-generic Expected: Sound to work, mic to work, sound card recognised in settings. What happened instead: Dummy sound only available card, sound does not work, mic does not work Tried: Restarting pulse audio, grepping lsmod for a sound card (nothing listed) Workaround: Everything works fine if I boot into 4.15.0-176-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1976160/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1975875] Re: libgail-3-0 install blocked by "=" dependency
Looking into this closer the libgtk 3.24.20 package is from focal- updates rather than focal. Once I reverted to 3.24.18 I could install Nemo without a problem. Not sure how the 20 package got onto what is essentially a brand new system, something else must have brought it in with it. That thing is probably broken now, hope it wasn't important. I'm still willing to provide information if you want it but it doesn't seem like this is an Ubuntu bug. Thanks for the help. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1975875 Title: libgail-3-0 install blocked by "=" dependency Status in gtk+3.0 package in Ubuntu: New Bug description: The libgtk dependency in libgail-3-0 is set to = *not* >= 3.24.18. Since libgtk has moved on to 3.24.20 the install of libgail is now blocked, which of course blocks everything that depends on it, Nemo in my case but I'm sure there are many others as well. Using Ubuntu 20.04 LTS with all current updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1975875/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1971468] Re: The upgrade will continue but the 'linux-image-5.13.0-39-generic' package may not be in a working state.
Unsure why this was reported against vim when the issue seems to be with other issues while attempting to upgrade to jammy. Moving to ubuntu-release-upgrader. Please let us know if you resolved the problem since reporting, thanks. ** Package changed: vim (Ubuntu) => ubuntu-release-upgrader (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1971468 Title: The upgrade will continue but the 'linux-image-5.13.0-39-generic' package may not be in a working state. Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: installed linux-image-5.13.0-39-generic package post-removal script subprocess returned error exit status 1 Ubuntu 22.04 Can not upgrade update Can not remove Brave Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 2767 (do-partial-upgr) Brave and Chrome keep crashing Ubuntu grub shows 2 ubuntu menu ( upgraded to 22.04 from 21.10 few days ago ), both ubuntu menu are openng ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: vim (not installed) ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 4 00:55:44 2022 InstallationDate: Installed on 2022-03-24 (40 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1971468/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1975875] Re: libgail-3-0 install blocked by "=" dependency
Days old Dell with Ubuntu 20.04 LTS, all latest updates installed. sudo apt install nemo fails with: The following packages have unmet dependencies: nemo : Depends: libgail-3-0 (>= 3.0.0) but it is not going to be installed E: Unable to correct problems, you have held broken packages. sudo apt install libgail-3-0 fails with: The following packages have unmet dependencies: libgail-3-0 : Depends: libgtk-3-0 (= 3.24.18-1ubuntu1) but 3.24.20-0ubuntu1.1 is to be installed E: Unable to correct problems, you have held broken packages. This page: https://packages.ubuntu.com/focal/libgail-3-0 shows that the requirement for libgtk is indeed "=" not ">=". All the other dependencies are ">=". I'm guessing that getting bitten by this is a side effect of it being a new system rather than one that's been updated over time. Happy to provide any other information that would be helpful. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1975875 Title: libgail-3-0 install blocked by "=" dependency Status in gtk+3.0 package in Ubuntu: New Bug description: The libgtk dependency in libgail-3-0 is set to = *not* >= 3.24.18. Since libgtk has moved on to 3.24.20 the install of libgail is now blocked, which of course blocks everything that depends on it, Nemo in my case but I'm sure there are many others as well. Using Ubuntu 20.04 LTS with all current updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1975875/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1975875] Re: libgail-3-0 install blocked by "=" dependency
Spun up a VM with fresh Unbuntu 20 and Nemo installed just fine, looks like this is fresh Dell install specific. Sorry for wasting your time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1975875 Title: libgail-3-0 install blocked by "=" dependency Status in gtk+3.0 package in Ubuntu: New Bug description: The libgtk dependency in libgail-3-0 is set to = *not* >= 3.24.18. Since libgtk has moved on to 3.24.20 the install of libgail is now blocked, which of course blocks everything that depends on it, Nemo in my case but I'm sure there are many others as well. Using Ubuntu 20.04 LTS with all current updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1975875/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970047] Re: GTK file open dialog hangs Chrome/Brave
/org/mate/desktop/sound/input-feedback-sounds actually fixed it for me (not /org/gnome). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1970047 Title: GTK file open dialog hangs Chrome/Brave Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: I removed xdg-desktop-portal because I use Xorg, don't use any snaps or flatpaks and GTK file open dialog is better than portal one. But GTK file open dialog makes Chrome/Brave freeze after closing it. Steps to reproduce: 1. Install Chrome or Brave 2. Remove xdg-desktop-portal so Chrome/Brave use GTK file open dialog instead of portal one 3. Press Ctrl+O to open file open dialog 4. Close dialog or choose any file, does not matter, browser is stuck I don't see this behavior on Debian that I also use, so I guess bug is in GTK rather than Chrome/Brave. Fresh install of Ubuntu 22.04 lsb_release: Description: Ubuntu 22.04 LTS Release: 22.04 libgtk-3-0: Installed: 3.24.33-1ubuntu1 Candidate: 3.24.33-1ubuntu1 Version table: *** 3.24.33-1ubuntu1 500 500 http://rs.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgtk-3-0 3.24.33-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 23 19:27:45 2022 InstallationDate: Installed on 2022-04-22 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1970047/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 827151] Re: Annoying log message "DIGEST-MD5 common mech free"
This bug was fixed in the package cyrus-sasl2 - 2.1.28+dfsg-6ubuntu1 --- cyrus-sasl2 (2.1.28+dfsg-6ubuntu1) kinetic; urgency=medium * d/p/0033-honor-log_level-option-on-clients-too.patch: honor log level option on clients (LP: #827151) -- Andreas Hasenack Wed, 25 May 2022 16:41:43 -0300 ** Changed in: cyrus-sasl2 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/827151 Title: Annoying log message "DIGEST-MD5 common mech free" Status in Cyrus-sasl2: Fix Released Status in cyrus-sasl2 package in Ubuntu: Fix Released Status in cyrus-sasl2 source package in Trusty: Won't Fix Status in cyrus-sasl2 source package in Xenial: Incomplete Status in cyrus-sasl2 source package in Yakkety: Fix Released Status in cyrus-sasl2 source package in Focal: Triaged Status in cyrus-sasl2 source package in Impish: Triaged Status in cyrus-sasl2 source package in Jammy: Triaged Status in cyrus-sasl2 package in Debian: Fix Released Bug description: I recently updated the libsasl2-modules to 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu1 in oneiric. That triggered the bug also described in Debian here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932 The annoying message is logged in auth.log. In my case, it is associated with svnserve: svnserve: DIGEST-MD5 common mech free I'm not exactly sure what action triggers the message, but I can investigate more if required. $ lsb_release -rd Description:Ubuntu oneiric (development branch) Release:11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/cyrus-sasl2/+bug/827151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1240336] Re: After release upgrade, the user loses permissions for several basic actions in the system
[Expired for lxdm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lxdm (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1240336 Title: After release upgrade, the user loses permissions for several basic actions in the system Status in gdm3 package in Ubuntu: Won't Fix Status in lightdm package in Ubuntu: Expired Status in lxdm package in Ubuntu: Expired Status in policykit-desktop-privileges package in Ubuntu: Expired Bug description: HOW TO REPRODUCE: - Upgrade Ubuntu to the next release. RESULT: - The user looses permissions for several basic actions in the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: policykit-desktop-privileges 0.16 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:20:55 2013 InstallationDate: Installed on 2013-10-09 (7 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: policykit-desktop-privileges UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1240336/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1240336] Re: After release upgrade, the user loses permissions for several basic actions in the system
[Expired for policykit-desktop-privileges (Ubuntu) because there has been no activity for 60 days.] ** Changed in: policykit-desktop-privileges (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1240336 Title: After release upgrade, the user loses permissions for several basic actions in the system Status in gdm3 package in Ubuntu: Won't Fix Status in lightdm package in Ubuntu: Expired Status in lxdm package in Ubuntu: Expired Status in policykit-desktop-privileges package in Ubuntu: Expired Bug description: HOW TO REPRODUCE: - Upgrade Ubuntu to the next release. RESULT: - The user looses permissions for several basic actions in the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: policykit-desktop-privileges 0.16 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:20:55 2013 InstallationDate: Installed on 2013-10-09 (7 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: policykit-desktop-privileges UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1240336/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1240336] Re: After release upgrade, the user loses permissions for several basic actions in the system
[Expired for lightdm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lightdm (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1240336 Title: After release upgrade, the user loses permissions for several basic actions in the system Status in gdm3 package in Ubuntu: Won't Fix Status in lightdm package in Ubuntu: Expired Status in lxdm package in Ubuntu: Expired Status in policykit-desktop-privileges package in Ubuntu: Expired Bug description: HOW TO REPRODUCE: - Upgrade Ubuntu to the next release. RESULT: - The user looses permissions for several basic actions in the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: policykit-desktop-privileges 0.16 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:20:55 2013 InstallationDate: Installed on 2013-10-09 (7 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: policykit-desktop-privileges UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1240336/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
