[Touch-packages] [Bug 1940377] Re: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute.
@Gabriel Can you also check linux-image-generic-hwe-20.04 on focal ? it's 5.11 as well. linux-image-generic-hwe-20.04 5.11.0.27.29~20.04.11 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1940377 Title: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute. Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: u@u-ThinkPad-L460:~$ uname -a Linux u-ThinkPad-L460 Kernel 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux u@u-ThinkPad-L460:~$ cat /etc/issue Ubuntu 21.04 \n \l CPU : Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz WWAN : 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module [Steps] 1. Make a Live CD for Ubuntu Hirsute 2. Plug in the Live CD 3. Boot ThinkPad L460 4. Install Ubuntu Hirsute and completed all configurations 5. Make sure the installation done 6. Boot the system and log in 7. Enable the proposed channel 8. Do the update and upgrade 9. Reboot the system and check mmcli is upgraded to 1.16.6 7. Verify the WWAN working or not. [Actual result] The WWAN can not be detected. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.16 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu Date: Wed Aug 18 01:32:17 2021 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IpRoute: default via 10.1.1.1 dev wlp3s0 proto dhcp metric 600 10.1.1.0/24 dev wlp3s0 proto kernel scope link src 10.1.1.106 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.30.0-1ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940377/+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 1869641] [NEW] Failed to launch ibus daemon in Xwayland + gnome-shell 3.36.0
Public bug reported: Description:Ubuntu Focal Fossa (development branch) Release:20.04 ibus 1.5.22-2ubuntu1 Steps to reproduce 1. Upgrade to GNOME 3.36.0. 2. Restart Ubuntu 20.04 daily with Wayland What did you expect to happen The ibus daemon is launched. What happened The ibus daemon is not running. I can confirm I have an exact same issue in https://gitlab.gnome.org/GNOME/gnome-shell/issues/2341 when login with wayland selected. After applying this: https://github.com/ibus/ibus/commit/8ce25208c3f4adfd290a032c6aa739d2b7580eb1 patch locally I can confirm it fixed my issue. ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: focal gnome-shell ibus wayland ** Tags added: focal gnome-shell ibus wayland -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1869641 Title: Failed to launch ibus daemon in Xwayland + gnome-shell 3.36.0 Status in ibus package in Ubuntu: New Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ibus 1.5.22-2ubuntu1 Steps to reproduce 1. Upgrade to GNOME 3.36.0. 2. Restart Ubuntu 20.04 daily with Wayland What did you expect to happen The ibus daemon is launched. What happened The ibus daemon is not running. I can confirm I have an exact same issue in https://gitlab.gnome.org/GNOME/gnome-shell/issues/2341 when login with wayland selected. After applying this: https://github.com/ibus/ibus/commit/8ce25208c3f4adfd290a032c6aa739d2b7580eb1 patch locally I can confirm it fixed my issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1869641/+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 1452238] Re: Failed to upgrade system from 14.04
#15 failed. I set intscripts as Pre-Depends (for ifupdown) but still not work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1452238 Title: Failed to upgrade system from 14.04 Status in ifupdown: New Status in ifupdown package in Ubuntu: Confirmed Bug description: Download and install the 14.04 image. http://cdimage.ubuntu.com/ubuntu/releases/14.04/release/ubuntu-14.04-desktop-amd64+mac.iso $ sudo apt-get update $ sudo apt-get upgrade . Processing triggers for desktop-file-utils (0.22-1ubuntu1) ... Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for mime-support (3.54ubuntu1) ... Processing triggers for hicolor-icon-theme (0.13-1) ... Processing triggers for gconf2 (3.2.6-0ubuntu2) ... Setting up libdbus-1-3:amd64 (1.6.18-0ubuntu4.3) ... Setting up libcgmanager0:amd64 (0.24-0ubuntu7.3) ... Setting up libudev1:amd64 (204-5ubuntu20.11) ... Processing triggers for libc-bin (2.19-0ubuntu6.6) ... (Reading database ... 163205 files and directories currently installed.) Preparing to unpack .../ifupdown_0.7.47.2ubuntu4.1_amd64.deb ... Unpacking ifupdown (0.7.47.2ubuntu4.1) over (0.7.47.2ubuntu4) ... Processing triggers for man-db (2.6.7.1-1) ... Processing triggers for ureadahead (0.100.0-16) ... dpkg: dependency problems prevent configuration of ifupdown: ifupdown depends on initscripts (= 2.88dsf-25); however: Package initscripts is not configured yet. dpkg: error processing package ifupdown (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ifupdown/+bug/1452238/+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 1452238] Re: Failed to upgrade system from 14.04
ifupdown depends on initscripts initscripts depends on upstart upstart depends on initscripts and ifupdown The error messages stats that dependency problems prevent configuration of ifupdown: ifupdown depends on initscripts (= 2.88dsf-25); however: Package initscripts is not configured yet. Upstart try to pull in ifupdown and initscripts, however, initscripts is already half-installed (because of other depenency), and ifupdown claim it depends on initscripts, so the apt broke at that stage. I think if we set initscripts as ifupdown's pre-depends, it could solve the problem. I'll try to verify this solution. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1452238 Title: Failed to upgrade system from 14.04 Status in ifupdown: New Status in ifupdown package in Ubuntu: Confirmed Bug description: Download and install the 14.04 image. http://cdimage.ubuntu.com/ubuntu/releases/14.04/release/ubuntu-14.04-desktop-amd64+mac.iso $ sudo apt-get update $ sudo apt-get upgrade . Processing triggers for desktop-file-utils (0.22-1ubuntu1) ... Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for mime-support (3.54ubuntu1) ... Processing triggers for hicolor-icon-theme (0.13-1) ... Processing triggers for gconf2 (3.2.6-0ubuntu2) ... Setting up libdbus-1-3:amd64 (1.6.18-0ubuntu4.3) ... Setting up libcgmanager0:amd64 (0.24-0ubuntu7.3) ... Setting up libudev1:amd64 (204-5ubuntu20.11) ... Processing triggers for libc-bin (2.19-0ubuntu6.6) ... (Reading database ... 163205 files and directories currently installed.) Preparing to unpack .../ifupdown_0.7.47.2ubuntu4.1_amd64.deb ... Unpacking ifupdown (0.7.47.2ubuntu4.1) over (0.7.47.2ubuntu4) ... Processing triggers for man-db (2.6.7.1-1) ... Processing triggers for ureadahead (0.100.0-16) ... dpkg: dependency problems prevent configuration of ifupdown: ifupdown depends on initscripts (= 2.88dsf-25); however: Package initscripts is not configured yet. dpkg: error processing package ifupdown (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ifupdown/+bug/1452238/+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 1452238] Re: Failed to upgrade system from 14.04
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/937196 it could be a similar bug like this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1452238 Title: Failed to upgrade system from 14.04 Status in ifupdown: New Status in ifupdown package in Ubuntu: Confirmed Bug description: Download and install the 14.04 image. http://cdimage.ubuntu.com/ubuntu/releases/14.04/release/ubuntu-14.04-desktop-amd64+mac.iso $ sudo apt-get update $ sudo apt-get upgrade . Processing triggers for desktop-file-utils (0.22-1ubuntu1) ... Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for mime-support (3.54ubuntu1) ... Processing triggers for hicolor-icon-theme (0.13-1) ... Processing triggers for gconf2 (3.2.6-0ubuntu2) ... Setting up libdbus-1-3:amd64 (1.6.18-0ubuntu4.3) ... Setting up libcgmanager0:amd64 (0.24-0ubuntu7.3) ... Setting up libudev1:amd64 (204-5ubuntu20.11) ... Processing triggers for libc-bin (2.19-0ubuntu6.6) ... (Reading database ... 163205 files and directories currently installed.) Preparing to unpack .../ifupdown_0.7.47.2ubuntu4.1_amd64.deb ... Unpacking ifupdown (0.7.47.2ubuntu4.1) over (0.7.47.2ubuntu4) ... Processing triggers for man-db (2.6.7.1-1) ... Processing triggers for ureadahead (0.100.0-16) ... dpkg: dependency problems prevent configuration of ifupdown: ifupdown depends on initscripts (= 2.88dsf-25); however: Package initscripts is not configured yet. dpkg: error processing package ifupdown (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ifupdown/+bug/1452238/+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 1452238] Re: Failed to upgrade system from 14.04
if upgrade ifupdown itself or using following commands there's no such issue #apt-get install --only-upgrade dpkg coreutils sysv-rc sysvinit-utils initscripts udev libudev1 ifupdown libc-bin upstart The failure during dist-upgrade/updrade by apt-get dist-upgrade is pretty weird. ** Attachment added: apt-success.log https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1452238/+attachment/4396603/+files/apt-success.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1452238 Title: Failed to upgrade system from 14.04 Status in ifupdown: New Status in ifupdown package in Ubuntu: Confirmed Bug description: Download and install the 14.04 image. http://cdimage.ubuntu.com/ubuntu/releases/14.04/release/ubuntu-14.04-desktop-amd64+mac.iso $ sudo apt-get update $ sudo apt-get upgrade . Processing triggers for desktop-file-utils (0.22-1ubuntu1) ... Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for mime-support (3.54ubuntu1) ... Processing triggers for hicolor-icon-theme (0.13-1) ... Processing triggers for gconf2 (3.2.6-0ubuntu2) ... Setting up libdbus-1-3:amd64 (1.6.18-0ubuntu4.3) ... Setting up libcgmanager0:amd64 (0.24-0ubuntu7.3) ... Setting up libudev1:amd64 (204-5ubuntu20.11) ... Processing triggers for libc-bin (2.19-0ubuntu6.6) ... (Reading database ... 163205 files and directories currently installed.) Preparing to unpack .../ifupdown_0.7.47.2ubuntu4.1_amd64.deb ... Unpacking ifupdown (0.7.47.2ubuntu4.1) over (0.7.47.2ubuntu4) ... Processing triggers for man-db (2.6.7.1-1) ... Processing triggers for ureadahead (0.100.0-16) ... dpkg: dependency problems prevent configuration of ifupdown: ifupdown depends on initscripts (= 2.88dsf-25); however: Package initscripts is not configured yet. dpkg: error processing package ifupdown (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ifupdown/+bug/1452238/+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 1452238] Re: Failed to upgrade system from 14.04
** Attachment added: aptitude.log https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1452238/+attachment/4396142/+files/aptitude.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1452238 Title: Failed to upgrade system from 14.04 Status in ifupdown: New Status in ifupdown package in Ubuntu: Confirmed Bug description: Download and install the 14.04 image. http://cdimage.ubuntu.com/ubuntu/releases/14.04/release/ubuntu-14.04-desktop-amd64+mac.iso $ sudo apt-get update $ sudo apt-get upgrade . Processing triggers for desktop-file-utils (0.22-1ubuntu1) ... Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for mime-support (3.54ubuntu1) ... Processing triggers for hicolor-icon-theme (0.13-1) ... Processing triggers for gconf2 (3.2.6-0ubuntu2) ... Setting up libdbus-1-3:amd64 (1.6.18-0ubuntu4.3) ... Setting up libcgmanager0:amd64 (0.24-0ubuntu7.3) ... Setting up libudev1:amd64 (204-5ubuntu20.11) ... Processing triggers for libc-bin (2.19-0ubuntu6.6) ... (Reading database ... 163205 files and directories currently installed.) Preparing to unpack .../ifupdown_0.7.47.2ubuntu4.1_amd64.deb ... Unpacking ifupdown (0.7.47.2ubuntu4.1) over (0.7.47.2ubuntu4) ... Processing triggers for man-db (2.6.7.1-1) ... Processing triggers for ureadahead (0.100.0-16) ... dpkg: dependency problems prevent configuration of ifupdown: ifupdown depends on initscripts (= 2.88dsf-25); however: Package initscripts is not configured yet. dpkg: error processing package ifupdown (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ifupdown/+bug/1452238/+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 1452238] Re: Failed to upgrade system from 14.04
Package: udev Source: systemd Version: 204-5ubuntu20kittyhawk1 Architecture: amd64 Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com Installed-Size: 5143 Depends: libacl1 (= 2.2.51-8), libblkid1 (= 2.19.1), libc6 (= 2.17), libcgmanager0, libdbus-1-3 (= 1.0.2), libkmod2 (= 5~), libnih-dbus1 (= 1.0.0), libnih1 (= 1.0.0), libselinux1 (= 2.0.65), libudev1 (= 204-5ubuntu20kittyhawk1), sysv-rc (= 2.88dsf-24) | file-rc (= 0.8.16), lsb-base (= 3.0-6), util-linux (= 2.16), procps Replaces: systemd-services ( 202-0ubuntu6) Section: admin Priority: important Multi-Arch: foreign not sure why but seems udev only depends on libc6, however libc6-dbg and libc6-dev depends on a old version of libc6, so it seems a loop dependency to me but I'm not sure why libc6-dbg and libc6-dev didn't get upgrade in the same time... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1452238 Title: Failed to upgrade system from 14.04 Status in ifupdown: New Status in ifupdown package in Ubuntu: Confirmed Bug description: Download and install the 14.04 image. http://cdimage.ubuntu.com/ubuntu/releases/14.04/release/ubuntu-14.04-desktop-amd64+mac.iso $ sudo apt-get update $ sudo apt-get upgrade . Processing triggers for desktop-file-utils (0.22-1ubuntu1) ... Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for mime-support (3.54ubuntu1) ... Processing triggers for hicolor-icon-theme (0.13-1) ... Processing triggers for gconf2 (3.2.6-0ubuntu2) ... Setting up libdbus-1-3:amd64 (1.6.18-0ubuntu4.3) ... Setting up libcgmanager0:amd64 (0.24-0ubuntu7.3) ... Setting up libudev1:amd64 (204-5ubuntu20.11) ... Processing triggers for libc-bin (2.19-0ubuntu6.6) ... (Reading database ... 163205 files and directories currently installed.) Preparing to unpack .../ifupdown_0.7.47.2ubuntu4.1_amd64.deb ... Unpacking ifupdown (0.7.47.2ubuntu4.1) over (0.7.47.2ubuntu4) ... Processing triggers for man-db (2.6.7.1-1) ... Processing triggers for ureadahead (0.100.0-16) ... dpkg: dependency problems prevent configuration of ifupdown: ifupdown depends on initscripts (= 2.88dsf-25); however: Package initscripts is not configured yet. dpkg: error processing package ifupdown (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ifupdown/+bug/1452238/+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 1452238] Re: Failed to upgrade system from 14.04
@4$ which command did you run at firsttime in https://pastebin.canonical.com/130750/ ? apt-get dist-upgrade or apt-get upgrade? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1452238 Title: Failed to upgrade system from 14.04 Status in ifupdown: New Status in ifupdown package in Ubuntu: Confirmed Bug description: Download and install the 14.04 image. http://cdimage.ubuntu.com/ubuntu/releases/14.04/release/ubuntu-14.04-desktop-amd64+mac.iso $ sudo apt-get update $ sudo apt-get upgrade . Processing triggers for desktop-file-utils (0.22-1ubuntu1) ... Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for mime-support (3.54ubuntu1) ... Processing triggers for hicolor-icon-theme (0.13-1) ... Processing triggers for gconf2 (3.2.6-0ubuntu2) ... Setting up libdbus-1-3:amd64 (1.6.18-0ubuntu4.3) ... Setting up libcgmanager0:amd64 (0.24-0ubuntu7.3) ... Setting up libudev1:amd64 (204-5ubuntu20.11) ... Processing triggers for libc-bin (2.19-0ubuntu6.6) ... (Reading database ... 163205 files and directories currently installed.) Preparing to unpack .../ifupdown_0.7.47.2ubuntu4.1_amd64.deb ... Unpacking ifupdown (0.7.47.2ubuntu4.1) over (0.7.47.2ubuntu4) ... Processing triggers for man-db (2.6.7.1-1) ... Processing triggers for ureadahead (0.100.0-16) ... dpkg: dependency problems prevent configuration of ifupdown: ifupdown depends on initscripts (= 2.88dsf-25); however: Package initscripts is not configured yet. dpkg: error processing package ifupdown (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ifupdown/+bug/1452238/+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 1452238] Re: Failed to upgrade system from 14.04
@Bin could we use #apt-get dist-upgrade instead? since that's what update-manager would do~ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1452238 Title: Failed to upgrade system from 14.04 Status in ifupdown: New Status in ifupdown package in Ubuntu: Confirmed Bug description: Download and install the 14.04 image. http://cdimage.ubuntu.com/ubuntu/releases/14.04/release/ubuntu-14.04-desktop-amd64+mac.iso $ sudo apt-get update $ sudo apt-get upgrade . Processing triggers for desktop-file-utils (0.22-1ubuntu1) ... Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for mime-support (3.54ubuntu1) ... Processing triggers for hicolor-icon-theme (0.13-1) ... Processing triggers for gconf2 (3.2.6-0ubuntu2) ... Setting up libdbus-1-3:amd64 (1.6.18-0ubuntu4.3) ... Setting up libcgmanager0:amd64 (0.24-0ubuntu7.3) ... Setting up libudev1:amd64 (204-5ubuntu20.11) ... Processing triggers for libc-bin (2.19-0ubuntu6.6) ... (Reading database ... 163205 files and directories currently installed.) Preparing to unpack .../ifupdown_0.7.47.2ubuntu4.1_amd64.deb ... Unpacking ifupdown (0.7.47.2ubuntu4.1) over (0.7.47.2ubuntu4) ... Processing triggers for man-db (2.6.7.1-1) ... Processing triggers for ureadahead (0.100.0-16) ... dpkg: dependency problems prevent configuration of ifupdown: ifupdown depends on initscripts (= 2.88dsf-25); however: Package initscripts is not configured yet. dpkg: error processing package ifupdown (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ifupdown/+bug/1452238/+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 1448900] [NEW] systemd-importd not found, breaks functionality of machinectl
Public bug reported: Steps to reproduce: Follow the example of MACHINECTL(1): #machinectl pull-tar https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-root.tar.gz Failed pull image: The name org.freedesktop.import1 was not provided by any .service files running on systemd 219-7ubuntu3 with vivid. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1448900 Title: systemd-importd not found, breaks functionality of machinectl Status in systemd package in Ubuntu: New Bug description: Steps to reproduce: Follow the example of MACHINECTL(1): #machinectl pull-tar https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-root.tar.gz Failed pull image: The name org.freedesktop.import1 was not provided by any .service files running on systemd 219-7ubuntu3 with vivid. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1448900/+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 1035431] Re: bluetooth-wizard failed to connect to a keyboard(logitech)
HP Bluetooth Keyboard K4000 worked fine with packages in trusty- proposed. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1035431 Title: bluetooth-wizard failed to connect to a keyboard(logitech) Status in GNOME Bluetooth: New Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: New Status in bluez package in Ubuntu: Fix Released Status in gnome-bluetooth package in Ubuntu: Fix Released Status in bluez source package in Precise: Triaged Status in gnome-bluetooth source package in Precise: Triaged Status in bluez source package in Trusty: Fix Committed Status in gnome-bluetooth source package in Trusty: Fix Committed Bug description: [Impact] * Fixes issues connecting bluetooth devices using SSP (Simple Secure Pairing); which does include many newer bluetooth devices, especially keyboards. [Test Case] * Try to connect a bluetooth keyboard using the wizard; especially one of the following models: Logitech Bluetooth Keyboard K760 Logitech Bluetooth Keyboard K810 HP Bluetooth Keyboard K4000 [Regression Potential] * It must be ensured that keyboards that could already be paired successfully still work properly; specifically, especially for keyboards but for any other devices, that pairing still works despite changes to the SSP code. [Other Info] --- When I try to connect my bluetooth keyboard using bluetooth-wizard, it ever fails: ** (bluetooth-wizard:11367): WARNING **: Setting up 'Logitech K760' failed: Authentication Failed This keyboard works fine with another computer under ubuntu 11.04. This keyboard works fine with this computer and Windows 7 (arghhh). This computer ubuntu 12.04 works fine with my bluetooth mouse. I can attach manually this keyboard to this computer using : sudo hidd --search My computer is a Samsung 305U1A My bluetooth interface is : Bus 003 Device 002: ID 0a5c:219c Broadcom Corp. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1035431/+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
