[Touch-packages] [Bug 2020110] Re: Migrate netplan settings to this package
Per discussions in the appropriate PR for Calamares[1], this should be done in network-manager itself. The appeal is more custom approaches. Downstreams and vendors of Ubuntu. [1] https://github.com/calamares/calamares/pull/2284 ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/2020110 Title: Migrate netplan settings to this package Status in network-manager package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: The current netplan configuration that specifies Network Manager as the renderer comes from a livecd-rootfs hack and results in an "unowned" file in /etc/netplan/01-use-network-manager.yaml. It was decided at the engineering sprint to migrate this to /lib/netplan (with a slightly tweaked filename starting 00- for precedence) owned by ubuntu-settings which will ease maintenance (and image builds) in future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2020110/+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 2020110] Re: Migrate netplan settings to this package
** Tags added: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2020110 Title: Migrate netplan settings to this package Status in network-manager package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: The current netplan configuration that specifies Network Manager as the renderer comes from a livecd-rootfs hack and results in an "unowned" file in /etc/netplan/01-use-network-manager.yaml. It was decided at the engineering sprint to migrate this to /lib/netplan (with a slightly tweaked filename starting 00- for precedence) owned by ubuntu-settings which will ease maintenance (and image builds) in future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2020110/+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 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
** Changed in: snapd (Ubuntu) Importance: Undecided => High ** Tags added: rls-nn-incoming -- 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/1951491 Title: Can't run snaps: .slice/session-1.scope is not a snap cgroup Status in X2Go: New Status in Xpra Terminal Server: New Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in x2goserver package in Ubuntu: Confirmed Status in snapd package in Debian: New Status in snapd package in Fedora: New Bug description: I just upgraded from hirsute to impish using do-release-upgrade. On the upgraded system, I can't run either firefox or chromium (both of which worked fine under hirsute). Both fail with: /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where NNN is my uid With firefox, I was able to fix the problem with: snap remove --purge firefox apt purge firefox apt install firefox Now firefox works. But I tried the same thing substituting chromium- browser for firefox, and it didn't help: chromium fails with the same error message. I guess there must be something left over from the hirsute version of snapd that isn't getting noticed or cleared by the impish version? Someone suggested this might be related to bug 1850667, but that bug is marked fixed as of a couple months ago, and I just did this upgrade today. Also, it doesn't mention the error message I'm seeing. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: snapd 2.53+21.10ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Nov 18 18:12:45 2021 InstallationDate: Installed on 2020-04-29 (568 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snapd UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/x2go/+bug/1951491/+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 2061214] Re: Software sources not correctly updated after upgrade and/or new installs
** Changed in: software-properties (Ubuntu) Assignee: (unassigned) => Simon Quigley (tsimonq2) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2061214 Title: Software sources not correctly updated after upgrade and/or new installs Status in software-properties package in Ubuntu: New Bug description: Upgrading Lubuntu Jammy to Lubuntu Noble using TUI results in "Software sources" not correctly updated after upgrade. Prompt= shows normal and not LTS Used command sudo do-release-upgrade -d Otherwise the upgrade is good see attached screenshot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: software-properties-common 0.99.46 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Apr 13 11:44:28 2024 InstallationDate: Installed on 2024-04-13 (0 days ago) InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240331) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-02-22T14:20:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2061214/+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 2061214] Re: Software sources not correctly updated after upgrade and/or new installs
** Changed in: software-properties (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2061214 Title: Software sources not correctly updated after upgrade and/or new installs Status in software-properties package in Ubuntu: Confirmed Bug description: Upgrading Lubuntu Jammy to Lubuntu Noble using TUI results in "Software sources" not correctly updated after upgrade. Prompt= shows normal and not LTS Used command sudo do-release-upgrade -d Otherwise the upgrade is good see attached screenshot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: software-properties-common 0.99.46 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Apr 13 11:44:28 2024 InstallationDate: Installed on 2024-04-13 (0 days ago) InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240331) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-02-22T14:20:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2061214/+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 2061214] Re: [SRU] Software Sources is not compatible with deb822
** Summary changed: - Software sources not correctly updated after upgrade and/or new installs + [SRU] Software Sources is not compatible with deb822 ** Summary changed: - [SRU] Software Sources is not compatible with deb822 + Software Sources is not compatible with deb822 ** Summary changed: - Software Sources is not compatible with deb822 + [SRU] Software Sources is not compatible with deb822 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2061214 Title: [SRU] Software Sources is not compatible with deb822 Status in software-properties package in Ubuntu: Confirmed Bug description: Upgrading Lubuntu Jammy to Lubuntu Noble using TUI results in "Software sources" not correctly updated after upgrade. Prompt= shows normal and not LTS Used command sudo do-release-upgrade -d Otherwise the upgrade is good see attached screenshot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: software-properties-common 0.99.46 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Apr 13 11:44:28 2024 InstallationDate: Installed on 2024-04-13 (0 days ago) InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240331) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-02-22T14:20:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2061214/+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 2061214] Re: [SRU] Software Sources is not compatible with deb822
** Description changed: + [ Impact ] + + Ubuntu 24.04 now uses deb822 to represent software sources for deb + packages, instead of /etc/apt/sources.list. The complete rationale for + this change can be found here: https://discourse.ubuntu.com/t/spec-apt- + deb822-sources-by-default/29333 + + software-properties has two graphical frontends for editing these + software sources, one is GTK-based and the other is Qt-based. When the + underlying change to deb822 sources was made, the GTK-based frontend and + the DBus backend interface gained support. + + The original bug report shown below informed us of the lack of deb822 + support in the Qt frontend, which results in a broken, non-functional + interface when attempting to view or edit most values on the first two + tabs. The fix for this is to implement a Qt dialog for deb822 sources + that somewhat matches the existing GTK interface. + + [ Test Plan ] + + Install software-properties-qt 0.99.48 or earlier. + + Reproducing the bug: + 1. From the menu, open Software Sources. Alternatively, run `sudo -E software-properties-qt` in a terminal. + 2. Observe that all four checkboxes on the Ubuntu Software tab (main, universe, restricted, and multiverse) are unchecked. + 3. Move to the Other Software tab and observe that there are no items in the list. + + Upgrade to software-properties-qt 0.99.49. + + Intended functionality: + 1. From the menu, open Software Sources. Alternatively, run `sudo -E software-properties-qt` in a terminal. + 2. Observe that one or more checkboxes on the Ubuntu Software tab (representing main, universe, restricted, or multiverse) are checked. Toggle one or more of the checkboxes. + 3. Using a text editor of some kind (perhaps Vim), confirm that /etc/apt/sources.list.d/ubuntu.sources reflects your changes. + 4. Switch to the Other Software tab, there should be one item in the list. + 5. Select that item, then click Edit at the bottom of the dialog. Make a modification to every field on the screen, or a combination of fields you would like to test. All fields should work. + 6. Click the OK button at the bottom of the dialog to confirm the changes, then click Edit for that item again. The changes you made should be reflected (meaning, the changes were saved.) + 7. Using a text editor of some kind (perhaps Vim), confirm that /etc/apt/sources.list.d/ubuntu.sources reflects your changes. + + [ Where problems could occur ] + + This is well-tested code. That being said, the following small edge cases exist: + - If you create a very large amount of rows, it infinitely expands the dialog without a scroll wheel. This is the same functionality as the GTK frontend. + - Error validation is not performed on the deb822 lines, they are simply written to the ubuntu.sources file. This is good as a starting point, but also relies on the appropriate update notifier handling these errors. This is the same functionality as the GTK frontend. + + In a future update, this functionality could be broken by one or more of the following underlying changes: + - Changes to the software-properties backend which are only implemented for the GTK frontend. + - Changes to the location or formatting of the ubuntu.sources file. + - Regressions in the Python bindings for Qt 5, which are rare but possible. + - Regressions in Python itself. + + [ Other Info ] + + Ubuntu Studio's live ISO and installed system are affected by this. Only Lubuntu's installed system is affected by this. + + [ Original Report ] + Upgrading Lubuntu Jammy to Lubuntu Noble using TUI results in "Software sources" not correctly updated after upgrade. Prompt= shows normal and not LTS Used command sudo do-release-upgrade -d Otherwise the upgrade is good see attached screenshot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: software-properties-common 0.99.46 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Apr 13 11:44:28 2024 InstallationDate: Installed on 2024-04-13 (0 days ago) InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240331) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-02-22T14:20:00 ** Also affects: software-properties (Ubuntu Noble) Importance: Critical Assignee: Simon Quigley (tsimonq2) Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2061214 Title: [SRU] Software Sources is not compatible with deb822 Status in software-properties package in Ubuntu: Confirmed Status in software-prop
[Touch-packages] [Bug 1999258] Re: Please merge dbus 1.14.4-1 from Debian unstable.
Looks like this was already sponsored: https://launchpad.net/ubuntu/+source/dbus/1.14.4-1ubuntu1 Please re-subscribe ~ubuntu-sponsors if further action is required. Thank you! -- 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/1999258 Title: Please merge dbus 1.14.4-1 from Debian unstable. Status in dbus package in Ubuntu: New Bug description: Please merge dbus 1.14.4-1 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1999258/+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 1864424] Re: new vim version in 20.04 sets mouse=a by default
** Changed in: vim (Ubuntu) Status: Fix Committed => Fix Released -- 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/1864424 Title: new vim version in 20.04 sets mouse=a by default Status in vim package in Ubuntu: Fix Released Bug description: Upgrading vim in Focal from 2:8.1.0875-5ubuntu4 to 2:8.1.2269-1ubuntu1 changed the default behavior. Old: :set mouse mouse= New: :set mouse mouse=a That new behavior prevents most peoples common In fact that is one thing that always annoys me when working with a Debian VM/Container to have switch to mouse=v to get things working again. Issues: - marking something with the mouse does NOT copy it anymore - marking something with the mouse does not even allow right-click to copy - probably more Yes I know one could press shift to get the old behavior, but that isn't how the rest of the terminal works. I'd much prefer to "press shift for the uncommon/new behavior". We always had in the changelog: - debian/patches/ubuntu-mouse-off.patch: + Mouse mode is actively harmful in some chroots. Old bug 1661691 brought that delta in early 2017 But this was dropped on the last merge: * Dropped changes, included upstream: - debian/patches/ubuntu-mouse-off.patch: + Mouse mode is actively harmful in some chroots. Yet if this would be upstream then the behavior would not have changed right? Was this change intentional and is there a good reason that makes up for the drawback? Or is it a bug that was missed on the merge of the new version and should be resolved before 20.04 goes into FF? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1864424/+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 2002428] Re: Autopkgtest failure due to moved testcase
Looks like this was sponsored (thanks William!), unsubscribing the sponsors team. ** Changed in: coreutils (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2002428 Title: Autopkgtest failure due to moved testcase Status in coreutils package in Ubuntu: Fix Committed Bug description: In 9.1-1ubuntu1 (lunar), a testcase has been renamed from proc- selinux-segfault.sh to selinux-segfault.sh . This changes debian/tests/upstream to reflect the change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2002428/+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 2003889] Re: Pleae merge wpa 2.10-10 from Debian
Hi Nathan! I have no problem with the patch, given the author. That being said, it would be useful to send this delta up to Debian if at all possible. Please consider it. :) Also, it's best not to modify changelog entries that exist in Debian. I'm dropping this before uploading: wpa (2:2.10-9) unstable; urgency=medium - [ Sebastien Bacher ] * debian/patches/allow-legacy-renegotiation.patch: -Allow legacy renegotiation to fix PEAP issues with some servers -(Closes: #1010603, LP: #1962541) +allow legacy renegotiation to fix PEAP issues with some servers +(Closes: #1010603) - -- Andrej Shadura Thu, 05 May 2022 11:23:33 +0100 + -- Sebastien Bacher Thu, 05 May 2022 11:31:26 +0200 Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/2003889 Title: Pleae merge wpa 2.10-10 from Debian Status in wpa package in Ubuntu: Confirmed Bug description: I built it successfully in Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/2003889/+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 2004092] Re: casper fails to add any users because GID 999 is already taken
> It's not clear to me that changing the casper user to use this uid won't badly confuse the installer when it comes time to create the actual user account, or at least cause gid 1000 to be skipped. It's not clear to me that it will. Casper doesn't touch the squashfs that ends up on the installed system, it simply creates a user in the overlay filesystem. If this does end up changing the installer behavior, that's an installer bug; it should only care about what is actually in the squashfs. (If there's another use case I'm failing to consider, let me know.) -- 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/2004092 Title: casper fails to add any users because GID 999 is already taken Status in casper package in Ubuntu: Fix Released Status in systemd package in Ubuntu: New Bug description: This bug is due to the latest systemd upload in Ubuntu. systemd- journald now uses GID 999, when casper explicitly sets the live user to that UID and GID. Rather than going through the painstaking task of updating systemd to use a *different* user, let's just update casper to use 1000, which is the first dynamically-allocated user account per Debian Policy[1]. [1] https://www.debian.org/doc/debian-policy/ch-opersys.html#uid-and- gid-classes [ Original Report ] Normally, when one first boots a live ISO, a desktop automatically appears, asking users if they want to try or install Ubuntu (or, in the case of Lubuntu, they are simply dropped into a working desktop with an installation desktop icon available). As of the Lubuntu ISO on January 27, 2023, this has stopped occuring. Plymouth shows the initial boot animation, but the user is then dropped to a solid black screen. No user input is accepted. Attempting to switch to a TTY and sign in fails with the default "lubuntu" username and a blank password (the error "Login incorrect" is displayed). On Ubuntu Desktop, the behavior is even stranger. Rather than being shown a "Try or Install Ubuntu" screen, an initial system setup wizard appears that takes the user through the process of creating a user account. On a live ISO. Only after this wizard is finished does the "Try or Install Ubuntu" screen appear. Attempting to log into a TTY using the default "ubuntu" username and a blank password fails the same way as Lubuntu does, if done before the wizard is finished. However, one can log into a TTY if they finish the wizard and then attempt to log into the TTY using the credentials provided during user account setup. This issue affects at least the Lubuntu ISOs as of January 27, 2023, and the Ubuntu Desktop ISO at least as of January 28, 2023 (it is assumed that the 27th ISO for Ubuntu Desktop is also broken). The ISO from the 26th is most likely unaffected as there is successful testing information for Lubuntu on the 26th, so something likely happened between the 26th and the 27th to cause this breakage. Steps to reproduce: 1. Download the latest Lunar daily ISO of Ubuntu Desktop or Lubuntu. 2. Boot the ISO (hardware is irrelevant - this appears to occur on both physical and virtual hardware). For Lubuntu: 3. Wait until you are dropped to a black, blank screen. 4. Wait a while, then attempt to switch to a TTY and attempt to log in using "lubuntu" as the username and a blank password. The login attempt will be denied. For Ubuntu Desktop: 3. Wait until you are provided with an initial system setup wizard. 4. Switch to a TTY and attempt to log in using "ubuntu" as the username and a blank password. The login attempt will be denied. 5. Switch back to the system setup wizard, and complete it. 6. After completing the wizard, switch to a TTY again and attempt to log in using the credentials provided to the wizard. The login attempt will be successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2004092/+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 2004092] Re: casper fails to add any users because GID 999 is already taken
** Changed in: systemd (Ubuntu) Status: New => Confirmed ** Changed in: systemd (Ubuntu) Importance: Undecided => High -- 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/2004092 Title: casper fails to add any users because GID 999 is already taken Status in casper package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Bug description: This bug is due to the latest systemd upload in Ubuntu. systemd- journald now uses GID 999, when casper explicitly sets the live user to that UID and GID. Rather than going through the painstaking task of updating systemd to use a *different* user, let's just update casper to use 1000, which is the first dynamically-allocated user account per Debian Policy[1]. [1] https://www.debian.org/doc/debian-policy/ch-opersys.html#uid-and- gid-classes [ Original Report ] Normally, when one first boots a live ISO, a desktop automatically appears, asking users if they want to try or install Ubuntu (or, in the case of Lubuntu, they are simply dropped into a working desktop with an installation desktop icon available). As of the Lubuntu ISO on January 27, 2023, this has stopped occuring. Plymouth shows the initial boot animation, but the user is then dropped to a solid black screen. No user input is accepted. Attempting to switch to a TTY and sign in fails with the default "lubuntu" username and a blank password (the error "Login incorrect" is displayed). On Ubuntu Desktop, the behavior is even stranger. Rather than being shown a "Try or Install Ubuntu" screen, an initial system setup wizard appears that takes the user through the process of creating a user account. On a live ISO. Only after this wizard is finished does the "Try or Install Ubuntu" screen appear. Attempting to log into a TTY using the default "ubuntu" username and a blank password fails the same way as Lubuntu does, if done before the wizard is finished. However, one can log into a TTY if they finish the wizard and then attempt to log into the TTY using the credentials provided during user account setup. This issue affects at least the Lubuntu ISOs as of January 27, 2023, and the Ubuntu Desktop ISO at least as of January 28, 2023 (it is assumed that the 27th ISO for Ubuntu Desktop is also broken). The ISO from the 26th is most likely unaffected as there is successful testing information for Lubuntu on the 26th, so something likely happened between the 26th and the 27th to cause this breakage. Steps to reproduce: 1. Download the latest Lunar daily ISO of Ubuntu Desktop or Lubuntu. 2. Boot the ISO (hardware is irrelevant - this appears to occur on both physical and virtual hardware). For Lubuntu: 3. Wait until you are dropped to a black, blank screen. 4. Wait a while, then attempt to switch to a TTY and attempt to log in using "lubuntu" as the username and a blank password. The login attempt will be denied. For Ubuntu Desktop: 3. Wait until you are provided with an initial system setup wizard. 4. Switch to a TTY and attempt to log in using "ubuntu" as the username and a blank password. The login attempt will be denied. 5. Switch back to the system setup wizard, and complete it. 6. After completing the wizard, switch to a TTY again and attempt to log in using the credentials provided to the wizard. The login attempt will be successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2004092/+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 2004092] Re: casper fails to add any users because GID 999 is already taken
> It's not clear to me that changing the casper user to use this uid won't badly confuse the installer when it comes time to create the actual user account, or at least cause gid 1000 to be skipped. After some testing with the newly-uploaded casper, I can confirm this is not the case. I tested with the following setups: - Ubuntu Budgie, with Ubiquity - Lubuntu, with Calamares - Ubuntu, with the ubuntu-desktop-installer snap The live user has UID/GID 1000 and so does the installed user, in all three cases. I would test OEM, except it doesn't make sense. There is already an initial OEM user created, which will have 1000 either way. That's expected behavior. On the casper side, I think everything is working as intended. -- 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/2004092 Title: casper fails to add any users because GID 999 is already taken Status in casper package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Bug description: This bug is due to the latest systemd upload in Ubuntu. systemd- journald now uses GID 999, when casper explicitly sets the live user to that UID and GID. Rather than going through the painstaking task of updating systemd to use a *different* user, let's just update casper to use 1000, which is the first dynamically-allocated user account per Debian Policy[1]. [1] https://www.debian.org/doc/debian-policy/ch-opersys.html#uid-and- gid-classes [ Original Report ] Normally, when one first boots a live ISO, a desktop automatically appears, asking users if they want to try or install Ubuntu (or, in the case of Lubuntu, they are simply dropped into a working desktop with an installation desktop icon available). As of the Lubuntu ISO on January 27, 2023, this has stopped occuring. Plymouth shows the initial boot animation, but the user is then dropped to a solid black screen. No user input is accepted. Attempting to switch to a TTY and sign in fails with the default "lubuntu" username and a blank password (the error "Login incorrect" is displayed). On Ubuntu Desktop, the behavior is even stranger. Rather than being shown a "Try or Install Ubuntu" screen, an initial system setup wizard appears that takes the user through the process of creating a user account. On a live ISO. Only after this wizard is finished does the "Try or Install Ubuntu" screen appear. Attempting to log into a TTY using the default "ubuntu" username and a blank password fails the same way as Lubuntu does, if done before the wizard is finished. However, one can log into a TTY if they finish the wizard and then attempt to log into the TTY using the credentials provided during user account setup. This issue affects at least the Lubuntu ISOs as of January 27, 2023, and the Ubuntu Desktop ISO at least as of January 28, 2023 (it is assumed that the 27th ISO for Ubuntu Desktop is also broken). The ISO from the 26th is most likely unaffected as there is successful testing information for Lubuntu on the 26th, so something likely happened between the 26th and the 27th to cause this breakage. Steps to reproduce: 1. Download the latest Lunar daily ISO of Ubuntu Desktop or Lubuntu. 2. Boot the ISO (hardware is irrelevant - this appears to occur on both physical and virtual hardware). For Lubuntu: 3. Wait until you are dropped to a black, blank screen. 4. Wait a while, then attempt to switch to a TTY and attempt to log in using "lubuntu" as the username and a blank password. The login attempt will be denied. For Ubuntu Desktop: 3. Wait until you are provided with an initial system setup wizard. 4. Switch to a TTY and attempt to log in using "ubuntu" as the username and a blank password. The login attempt will be denied. 5. Switch back to the system setup wizard, and complete it. 6. After completing the wizard, switch to a TTY again and attempt to log in using the credentials provided to the wizard. The login attempt will be successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2004092/+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 2004039] Re: libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with bigger page sizes
Hi Tobias, thanks for your interest in this bug! While I did not do a code review of the patch itself, I have some general feedback on the diff and the bug report itself that I hope you find helpful: - The version should be 1.6.2-0ubuntu1.1 instead of 1.6.2-0ubuntu2, following Stable Release Update guidelines. Generally speaking, 1.6.2-0ubuntu2 would only be appropriate for the development release. - As a sponsor, I prefer DEP-3 headers[1] over Git patch headers, so the patch stays machine-readable (and so bug references such as this one and the Debian bug can be inserted). - The bug report description should be more thorough; does Xorg hard-crash, or is there a workaround? Could you provide specific instructions to reproduce the failure, please? Same with verification steps. For now, I'm unsubscribing the sponsors team. Please resubscribe the team once most (or all) of these points have been addressed. Thank you! [1] https://dep-team.pages.debian.net/deps/dep3/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/2004039 Title: libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with bigger page sizes Status in libunwind package in Ubuntu: New Status in libunwind source package in Kinetic: New Bug description: [ Impact ] * On kernels with page size > 4K xorg (and presumably other applications relying on libunwind) crashes on startup. This affects anyone running the official arm64 generic-64k kernel or custom non 4k kernels (as used by e.g. apple silicon). [ Test Plan ] * Make sure Xorg works on a variety of different archs and kernels with different page sizes. [ Where problems could occur ] * We will have to make sure the fixed version still works with 4k kernels. The patch is already widely in use so the risk seems low if we test properly. [ Other Info ] * The lunar version ships the bug fix synced from debian * Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026217 * Upstream fix: https://github.com/libunwind/libunwind/commit/e85b65cec757ef589f28957d0c6c21c498a03bdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/2004039/+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 2004092] Re: casper fails to add any users because GID 999 is already taken
Just to catch the bug report up with the IRC discussion: we got away with it in casper because we knew there weren't going to be 899 IDs allocated in this range in the installer context, and the casper user goes away post-install systemd doesn't statically set them, it allocates them using "first available" ID at boot time; however, it seems to start checking "first available" from the other direction from a policy perspective, I think the biggest bug is: policy says to use adduser; adduser has a config file that lets the admin change the allowed range (to subset it, perhaps, for compatibility with "legacy" IDs shared across an authentication domain); systemd doesn't honor adduser.conf but instead has its limit hard-coded at build time vorlon: I'll look into the adduser.conf piece specifically. But note that we as a distro can configure systemd's boundaries at build time enr0n: yes, but the disconnect is with it not honoring changes specified by the admin at runtime -- 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/2004092 Title: casper fails to add any users because GID 999 is already taken Status in casper package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Bug description: This bug is due to the latest systemd upload in Ubuntu. systemd- journald now uses GID 999, when casper explicitly sets the live user to that UID and GID. Rather than going through the painstaking task of updating systemd to use a *different* user, let's just update casper to use 1000, which is the first dynamically-allocated user account per Debian Policy[1]. [1] https://www.debian.org/doc/debian-policy/ch-opersys.html#uid-and- gid-classes [ Original Report ] Normally, when one first boots a live ISO, a desktop automatically appears, asking users if they want to try or install Ubuntu (or, in the case of Lubuntu, they are simply dropped into a working desktop with an installation desktop icon available). As of the Lubuntu ISO on January 27, 2023, this has stopped occuring. Plymouth shows the initial boot animation, but the user is then dropped to a solid black screen. No user input is accepted. Attempting to switch to a TTY and sign in fails with the default "lubuntu" username and a blank password (the error "Login incorrect" is displayed). On Ubuntu Desktop, the behavior is even stranger. Rather than being shown a "Try or Install Ubuntu" screen, an initial system setup wizard appears that takes the user through the process of creating a user account. On a live ISO. Only after this wizard is finished does the "Try or Install Ubuntu" screen appear. Attempting to log into a TTY using the default "ubuntu" username and a blank password fails the same way as Lubuntu does, if done before the wizard is finished. However, one can log into a TTY if they finish the wizard and then attempt to log into the TTY using the credentials provided during user account setup. This issue affects at least the Lubuntu ISOs as of January 27, 2023, and the Ubuntu Desktop ISO at least as of January 28, 2023 (it is assumed that the 27th ISO for Ubuntu Desktop is also broken). The ISO from the 26th is most likely unaffected as there is successful testing information for Lubuntu on the 26th, so something likely happened between the 26th and the 27th to cause this breakage. Steps to reproduce: 1. Download the latest Lunar daily ISO of Ubuntu Desktop or Lubuntu. 2. Boot the ISO (hardware is irrelevant - this appears to occur on both physical and virtual hardware). For Lubuntu: 3. Wait until you are dropped to a black, blank screen. 4. Wait a while, then attempt to switch to a TTY and attempt to log in using "lubuntu" as the username and a blank password. The login attempt will be denied. For Ubuntu Desktop: 3. Wait until you are provided with an initial system setup wizard. 4. Switch to a TTY and attempt to log in using "ubuntu" as the username and a blank password. The login attempt will be denied. 5. Switch back to the system setup wizard, and complete it. 6. After completing the wizard, switch to a TTY again and attempt to log in using the credentials provided to the wizard. The login attempt will be successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2004092/+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 2004092] Re: casper fails to add any users because GID 999 is already taken
** Bug watch added: Debian Bug tracker #1029785 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029785 ** Also affects: systemd (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029785 Importance: Unknown Status: Unknown -- 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/2004092 Title: casper fails to add any users because GID 999 is already taken Status in casper package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in systemd package in Debian: Unknown Bug description: This bug is due to the latest systemd upload in Ubuntu. systemd- journald now uses GID 999, when casper explicitly sets the live user to that UID and GID. Rather than going through the painstaking task of updating systemd to use a *different* user, let's just update casper to use 1000, which is the first dynamically-allocated user account per Debian Policy[1]. [1] https://www.debian.org/doc/debian-policy/ch-opersys.html#uid-and- gid-classes [ Original Report ] Normally, when one first boots a live ISO, a desktop automatically appears, asking users if they want to try or install Ubuntu (or, in the case of Lubuntu, they are simply dropped into a working desktop with an installation desktop icon available). As of the Lubuntu ISO on January 27, 2023, this has stopped occuring. Plymouth shows the initial boot animation, but the user is then dropped to a solid black screen. No user input is accepted. Attempting to switch to a TTY and sign in fails with the default "lubuntu" username and a blank password (the error "Login incorrect" is displayed). On Ubuntu Desktop, the behavior is even stranger. Rather than being shown a "Try or Install Ubuntu" screen, an initial system setup wizard appears that takes the user through the process of creating a user account. On a live ISO. Only after this wizard is finished does the "Try or Install Ubuntu" screen appear. Attempting to log into a TTY using the default "ubuntu" username and a blank password fails the same way as Lubuntu does, if done before the wizard is finished. However, one can log into a TTY if they finish the wizard and then attempt to log into the TTY using the credentials provided during user account setup. This issue affects at least the Lubuntu ISOs as of January 27, 2023, and the Ubuntu Desktop ISO at least as of January 28, 2023 (it is assumed that the 27th ISO for Ubuntu Desktop is also broken). The ISO from the 26th is most likely unaffected as there is successful testing information for Lubuntu on the 26th, so something likely happened between the 26th and the 27th to cause this breakage. Steps to reproduce: 1. Download the latest Lunar daily ISO of Ubuntu Desktop or Lubuntu. 2. Boot the ISO (hardware is irrelevant - this appears to occur on both physical and virtual hardware). For Lubuntu: 3. Wait until you are dropped to a black, blank screen. 4. Wait a while, then attempt to switch to a TTY and attempt to log in using "lubuntu" as the username and a blank password. The login attempt will be denied. For Ubuntu Desktop: 3. Wait until you are provided with an initial system setup wizard. 4. Switch to a TTY and attempt to log in using "ubuntu" as the username and a blank password. The login attempt will be denied. 5. Switch back to the system setup wizard, and complete it. 6. After completing the wizard, switch to a TTY again and attempt to log in using the credentials provided to the wizard. The login attempt will be successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2004092/+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 2002660] Re: networkx incompatible with numpy 1.24
** Tags removed: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2002660
Title:
networkx incompatible with numpy 1.24
Status in networkx package in Ubuntu:
Fix Released
Status in nipype package in Ubuntu:
Invalid
Status in python3-defaults package in Ubuntu:
Invalid
Bug description:
The nipype autopkgtests have started failing with the following stack
trace:
ERROR collecting pipeline/plugins/tests/test_tools.py
_
/usr/lib/python3.10/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
:1050: in _gcd_import
???
:1027: in _find_and_load
???
:992: in _find_and_load_unlocked
???
:241: in _call_with_frames_removed
???
:1050: in _gcd_import
???
:1027: in _find_and_load
???
:992: in _find_and_load_unlocked
???
:241: in _call_with_frames_removed
???
:1050: in _gcd_import
???
:1027: in _find_and_load
???
:1006: in _find_and_load_unlocked
???
:688: in _load_unlocked
???
:883: in exec_module
???
:241: in _call_with_frames_removed
???
nipype/pipeline/plugins/__init__.py:5: in
from .debug import DebugPlugin
nipype/pipeline/plugins/debug.py:7: in
import networkx as nx
/usr/lib/python3/dist-packages/networkx/__init__.py:115: in
import networkx.readwrite
/usr/lib/python3/dist-packages/networkx/readwrite/__init__.py:15: in
from networkx.readwrite.graphml import *
/usr/lib/python3/dist-packages/networkx/readwrite/graphml.py:314: in
class GraphML(object):
/usr/lib/python3/dist-packages/networkx/readwrite/graphml.py:346: in GraphML
(np.int, "int"), (np.int8, "int"),
/usr/lib/python3/dist-packages/numpy/__init__.py:284: in __getattr__
raise AttributeError("module {!r} has no attribute "
E AttributeError: module 'numpy' has no attribute 'int'
The problematic code is in the networkx package, and seems to have
been fixed in
https://github.com/networkx/networkx/commit/207147ee179554a33f10f25032054d3e01f96188
(which is in 2.5 onwards).
Debian currently ships with 2.8.8, we might want to merge?
This is currently blocking the python3-defaults transition.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/networkx/+bug/2002660/+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 2004039] Re: libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with bigger page sizes
LGTM, sponsored, thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/2004039 Title: libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with bigger page sizes Status in libunwind package in Ubuntu: New Status in libunwind source package in Kinetic: New Bug description: [ Impact ]  * On kernels with page size > 4K Xorg (and presumably other applications    relying on libunwind) crashes on startup. This affects anyone    running the official arm64 generic-64k kernel or custom non 4k kernels    (as used by e.g. apple silicon). The exact error I am seeing in the logs is: Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x188) [0xaaab456ca998] Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) unw_get_proc_info failed: no unwind info found [-10] Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) Segmentation fault at address 0x0 Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: Fatal server error: Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) Caught signal 11 (Segmentation fault). Server aborting Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: Please consult the The X.Org Foundation support Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: at http://wiki.x.org Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: for help. Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) I have not found a workaround other than using wayland (which has other limitations). To reproduce use a kernel configured with a page size of 16K (CONFIG_ARM64_16K_PAGES=y or CONFIG_ARM64_64K_PAGES=y or) and try to start "Ubuntu on Xorg" in gdm. [ Test Plan ]  * Make sure Xorg doesn't crash on 4K, 16K and 64K kernels. [ Where problems could occur ]  * We will have to make sure the fixed version still works with 4k    kernels. The patch is already widely in use so the risk seems low if    we test properly. [ Other Info ]  * The lunar version ships the bug fix synced from debian  * Debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1026217  * Upstream fix: https://github.com/libunwind/libunwind/commit/e85b65cec757ef589f28957d0c6c21c498a03bdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/2004039/+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 2004092] Re: casper fails to add any users because GID 999 is already taken
> the next casper upload will regress the current version of the fix I'm all in favor of a better longer-term fix replacing this one being tracked in systemd, but an unrelated casper upload regressing this change prior to a longer-term solution being in place will cause issues with all amd64 live ISOs. As noted above, this change does not present Ubiquity, ubuntu-desktop- installer, or Calamares from assigning a UID and GID of 1000 to the installed user, which is the same as it was before. What is the rationale for reverting this change? -- 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/2004092 Title: casper fails to add any users because GID 999 is already taken Status in casper package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in systemd package in Debian: Unknown Bug description: This bug is due to the latest systemd upload in Ubuntu. systemd- journald now uses GID 999, when casper explicitly sets the live user to that UID and GID. Rather than going through the painstaking task of updating systemd to use a *different* user, let's just update casper to use 1000, which is the first dynamically-allocated user account per Debian Policy[1]. [1] https://www.debian.org/doc/debian-policy/ch-opersys.html#uid-and- gid-classes [ Original Report ] Normally, when one first boots a live ISO, a desktop automatically appears, asking users if they want to try or install Ubuntu (or, in the case of Lubuntu, they are simply dropped into a working desktop with an installation desktop icon available). As of the Lubuntu ISO on January 27, 2023, this has stopped occuring. Plymouth shows the initial boot animation, but the user is then dropped to a solid black screen. No user input is accepted. Attempting to switch to a TTY and sign in fails with the default "lubuntu" username and a blank password (the error "Login incorrect" is displayed). On Ubuntu Desktop, the behavior is even stranger. Rather than being shown a "Try or Install Ubuntu" screen, an initial system setup wizard appears that takes the user through the process of creating a user account. On a live ISO. Only after this wizard is finished does the "Try or Install Ubuntu" screen appear. Attempting to log into a TTY using the default "ubuntu" username and a blank password fails the same way as Lubuntu does, if done before the wizard is finished. However, one can log into a TTY if they finish the wizard and then attempt to log into the TTY using the credentials provided during user account setup. This issue affects at least the Lubuntu ISOs as of January 27, 2023, and the Ubuntu Desktop ISO at least as of January 28, 2023 (it is assumed that the 27th ISO for Ubuntu Desktop is also broken). The ISO from the 26th is most likely unaffected as there is successful testing information for Lubuntu on the 26th, so something likely happened between the 26th and the 27th to cause this breakage. Steps to reproduce: 1. Download the latest Lunar daily ISO of Ubuntu Desktop or Lubuntu. 2. Boot the ISO (hardware is irrelevant - this appears to occur on both physical and virtual hardware). For Lubuntu: 3. Wait until you are dropped to a black, blank screen. 4. Wait a while, then attempt to switch to a TTY and attempt to log in using "lubuntu" as the username and a blank password. The login attempt will be denied. For Ubuntu Desktop: 3. Wait until you are provided with an initial system setup wizard. 4. Switch to a TTY and attempt to log in using "ubuntu" as the username and a blank password. The login attempt will be denied. 5. Switch back to the system setup wizard, and complete it. 6. After completing the wizard, switch to a TTY again and attempt to log in using the credentials provided to the wizard. The login attempt will be successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2004092/+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 2006633] Re: Merge librsvg 2.54.5+dfsg-1 (main) from Debian unstable (main)
Please remember to mention the bug number in the changelog entry. Additionally, for stylistic purposes, I changed this: * Merge from Debian unstable. The remaining difference is the change for ignoring test results on i386 to avoir failure. To this: * Merge from Debian Unstable (LP: #2006633). Remaining changes: - Don't fail the build on tests error for i386 Otherwise, looks good to me, uploading. Please keep this in mind for a later upload. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/2006633 Title: Merge librsvg 2.54.5+dfsg-1 (main) from Debian unstable (main) Status in librsvg package in Ubuntu: New Bug description: Please merge librsvg 2.54.5+dfsg-1 (main) from Debian unstable (main) Changelog entries since current lunar version 2.54.4+dfsg-1ubuntu1: librsvg (2.54.5+dfsg-1) unstable; urgency=medium * New upstream release * debian/librsvg2-2.docs: NEWS.md -> NEWS -- Jeremy Bicha Thu, 22 Sep 2022 17:00:54 -0400 Remaining differences with librsvg from Debian unstable: * Don't fail the build on tests error for i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/2006633/+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 2007421] Re: Please merge sysvinit 3.06-2 (main) from Debian unstable (main)
It looks like this upload has already been sponsored, thanks. ** Changed in: sysvinit (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/2007421 Title: Please merge sysvinit 3.06-2 (main) from Debian unstable (main) Status in sysvinit package in Ubuntu: Fix Committed Bug description: Debian moved from 3.05-7 to new upstream 3.06-2. As usual, we still only want to build sysvinit-utils and not the other binary packages. https://salsa.debian.org/debian/sysvinit/-/merge_requests/8 has not yet been merged so we need to carry the following patch: d/rules: fix installation of 50-ubuntu-logging when building on Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/2007421/+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 2008123] Re: Please merge 7.88.1-1 into lunar
** Changed in: curl (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/2008123 Title: Please merge 7.88.1-1 into lunar Status in curl package in Ubuntu: Fix Committed Bug description: PPA https://launchpad.net/~danilogondolfo/+archive/ubuntu/curl/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2008123/+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 2007698] Re: Please merge 1.9.13p1-1 into lunar
** Changed in: sudo (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/2007698 Title: Please merge 1.9.13p1-1 into lunar Status in sudo package in Ubuntu: Fix Committed Bug description: PPA available at https://launchpad.net/~danilogondolfo/+archive/ubuntu/sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2007698/+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 2007623] Re: Merge grilo-plugins 0.3.15-2 (universe) from Debian unstable (main)
Sponsored, thank you! ** Changed in: grilo-plugins (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/2007623 Title: Merge grilo-plugins 0.3.15-2 (universe) from Debian unstable (main) Status in grilo-plugins package in Ubuntu: Fix Committed Bug description: Please merge grilo-plugins 0.3.15-2 (universe) from Debian unstable (main) Changelog entries since current lunar version 0.3.15-1ubuntu1: grilo-plugins (0.3.15-2) unstable; urgency=medium * debian/control: - Stop recommending dleyna-server (Closes: #1030125). - Update Standards-Version to 4.6.2 (no changes). * debian/copyright: - Update copyright years. -- Alberto Garcia Tue, 31 Jan 2023 16:45:49 +0100 Remaining differences with grilo-plugins from Debian unstable: - Split package into -base and -extra (Closes: #805609) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/2007623/+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 2040011] [NEW] [SRU] Ensure supported codenames are accurate
Public bug reported: In several stable releases of Ubuntu, Vim has information regarding releases that are outdated. It would be optimal for Vim to grab this data from distro-info-data (or similar), but unfortunately that is not the case. Therefore, the list needs to be updated. There is a minimal regression potential here; Vim simply reads a statically-set Perl array to determine if the release in the changelog and sources.list is supported or not. Any regression would present itself in external tooling that detects text highlighting, which is not a case I think we support in Ubuntu. A simple way to test this update is to download a package from the Lunar archive, and open the changelog with Vim. Instead of the changelog release (e.g. "noble") showing as red, it should show as blue. I would also suggest editing sources.list, to ensure e.g. Eoan shows as EOL. ** Affects: vim (Ubuntu) Importance: Wishlist Assignee: Simon Quigley (tsimonq2) Status: In Progress ** Affects: vim (Ubuntu Focal) Importance: Wishlist Assignee: Simon Quigley (tsimonq2) Status: In Progress ** Affects: vim (Ubuntu Jammy) Importance: Wishlist Assignee: Simon Quigley (tsimonq2) Status: In Progress ** Affects: vim (Ubuntu Lunar) Importance: Wishlist Assignee: Simon Quigley (tsimonq2) Status: In Progress ** Affects: vim (Ubuntu Mantic) Importance: Wishlist Assignee: Simon Quigley (tsimonq2) Status: In Progress ** Also affects: vim (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: vim (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: vim (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: vim (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: vim (Ubuntu Focal) Assignee: (unassigned) => Simon Quigley (tsimonq2) ** Changed in: vim (Ubuntu Jammy) Assignee: (unassigned) => Simon Quigley (tsimonq2) ** Changed in: vim (Ubuntu Lunar) Assignee: (unassigned) => Simon Quigley (tsimonq2) ** Changed in: vim (Ubuntu Mantic) Assignee: (unassigned) => Simon Quigley (tsimonq2) ** Changed in: vim (Ubuntu Focal) Status: New => In Progress ** Changed in: vim (Ubuntu Jammy) Status: New => In Progress ** Changed in: vim (Ubuntu Lunar) Status: New => In Progress ** Changed in: vim (Ubuntu Mantic) Status: New => In Progress ** Changed in: vim (Ubuntu Focal) Importance: Undecided => Wishlist ** Changed in: vim (Ubuntu Jammy) Importance: Undecided => Wishlist ** Changed in: vim (Ubuntu Lunar) Importance: Undecided => Wishlist ** Changed in: vim (Ubuntu Mantic) Importance: Undecided => Wishlist -- 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/2040011 Title: [SRU] Ensure supported codenames are accurate Status in vim package in Ubuntu: In Progress Status in vim source package in Focal: In Progress Status in vim source package in Jammy: In Progress Status in vim source package in Lunar: In Progress Status in vim source package in Mantic: In Progress Bug description: In several stable releases of Ubuntu, Vim has information regarding releases that are outdated. It would be optimal for Vim to grab this data from distro-info-data (or similar), but unfortunately that is not the case. Therefore, the list needs to be updated. There is a minimal regression potential here; Vim simply reads a statically-set Perl array to determine if the release in the changelog and sources.list is supported or not. Any regression would present itself in external tooling that detects text highlighting, which is not a case I think we support in Ubuntu. A simple way to test this update is to download a package from the Lunar archive, and open the changelog with Vim. Instead of the changelog release (e.g. "noble") showing as red, it should show as blue. I would also suggest editing sources.list, to ensure e.g. Eoan shows as EOL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2040011/+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 1996087] Re: Ensure supported codenames are accurate
** Changed in: vim (Ubuntu Lunar) Status: Fix Committed => Fix Released -- 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/1996087 Title: Ensure supported codenames are accurate Status in vim package in Ubuntu: Fix Committed Status in vim source package in Focal: Fix Released Status in vim source package in Jammy: Fix Released Status in vim source package in Kinetic: Won't Fix Status in vim source package in Lunar: Fix Released Bug description: In several stable releases of Ubuntu, Vim has information regarding releases that are outdated. It would be optimal for Vim to grab this data from distro-info-data (or similar), but unfortunately that is not the case. Therefore, the list needs to be updated. There is a minimal regression potential here; Vim simply reads a statically-set Perl array to determine if the release in the changelog and sources.list is supported or not. Any regression would present itself in external tooling that detects text highlighting, which is not a case I think we support in Ubuntu. A simple way to test this update is to download a package from the Lunar archive, and open the changelog with Vim. Instead of the changelog release (e.g. "lunar") showing as red, it should show as blue. I would also suggest editing sources.list, to ensure e.g. Eoan shows as EOL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1996087/+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 2043713] [NEW] armhf autopkgtests fail due to TestApportValgrind.test_valgrind_min_installed
Public bug reported: autopkgtests are pretty reliably failing[1] on armhf due to the following (single) test failure: 638s === FAILURES === 638s TestApportValgrind.test_valgrind_min_installed 638s 638s self = 638s 638s def test_valgrind_min_installed(self): 638s """Valgrind is installed and recent enough.""" 638s cmd = ["valgrind", "-q", "--extra-debuginfo-path=./", "ls"] 638s (ret, out, err) = self._call(cmd) 638s > self.assertEqual(err, "") 638s E AssertionError: "==2474== Invalid write of size 4\n==2474[1064 chars]= \n" != '' 638s E Diff is 1134 characters long. Set self.maxDiff to None to see it. 638s 638s tests/integration/test_apport_valgrind.py:43: AssertionError This could be related to valgrind functionality being different on armhf, it could also be related to integer sizes internally on armhf. I haven't looked too deeply into it. [1] https://autopkgtest.ubuntu.com/packages/a/apport/noble/armhf ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2043713 Title: armhf autopkgtests fail due to TestApportValgrind.test_valgrind_min_installed Status in apport package in Ubuntu: New Bug description: autopkgtests are pretty reliably failing[1] on armhf due to the following (single) test failure: 638s === FAILURES === 638s TestApportValgrind.test_valgrind_min_installed 638s 638s self = 638s 638s def test_valgrind_min_installed(self): 638s """Valgrind is installed and recent enough.""" 638s cmd = ["valgrind", "-q", "--extra-debuginfo-path=./", "ls"] 638s (ret, out, err) = self._call(cmd) 638s > self.assertEqual(err, "") 638s E AssertionError: "==2474== Invalid write of size 4\n==2474[1064 chars]= \n" != '' 638s E Diff is 1134 characters long. Set self.maxDiff to None to see it. 638s 638s tests/integration/test_apport_valgrind.py:43: AssertionError This could be related to valgrind functionality being different on armhf, it could also be related to integer sizes internally on armhf. I haven't looked too deeply into it. [1] https://autopkgtest.ubuntu.com/packages/a/apport/noble/armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2043713/+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 2043713] Re: armhf autopkgtests fail due to TestApportValgrind.test_valgrind_min_installed
** Tags added: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2043713 Title: armhf autopkgtests fail due to TestApportValgrind.test_valgrind_min_installed Status in apport package in Ubuntu: New Bug description: autopkgtests are pretty reliably failing[1] on armhf due to the following (single) test failure: 638s === FAILURES === 638s TestApportValgrind.test_valgrind_min_installed 638s 638s self = 638s 638s def test_valgrind_min_installed(self): 638s """Valgrind is installed and recent enough.""" 638s cmd = ["valgrind", "-q", "--extra-debuginfo-path=./", "ls"] 638s (ret, out, err) = self._call(cmd) 638s > self.assertEqual(err, "") 638s E AssertionError: "==2474== Invalid write of size 4\n==2474[1064 chars]= \n" != '' 638s E Diff is 1134 characters long. Set self.maxDiff to None to see it. 638s 638s tests/integration/test_apport_valgrind.py:43: AssertionError This could be related to valgrind functionality being different on armhf, it could also be related to integer sizes internally on armhf. I haven't looked too deeply into it. [1] https://autopkgtest.ubuntu.com/packages/a/apport/noble/armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2043713/+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 2044015] Re: please merge cron 3.0pl1-178 from Debian unstable
** Changed in: cron (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/2044015 Title: please merge cron 3.0pl1-178 from Debian unstable Status in cron package in Ubuntu: Fix Committed Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/2044015/+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 2022927] Re: Busybox mount fails to mount Snaps
** Changed in: busybox (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/2022927 Title: Busybox mount fails to mount Snaps Status in busybox package in Ubuntu: Incomplete Bug description: Snapd tries to mount squashfs Snaps with non-standard mount flags like "x-gdu.hide" and "x-gvfs-hide", both of which are used to indicate to userspace programs that a given mount should not be shown in a list of mounted partitions/filesystems. Busybox does not support these flags, and so fails with "Invalid argument". $ sudo busybox mount -t tmpfs -o x-gdu-hide test /tmp/test mount: mounting test on /tmp/test failed: Invalid argument These flags can likely be be safely ignored, as they don't actually affect the functionality of the mount. This goes for all mount options starting with "x-", as these generally denote non-standard mount option "extensions". I've created a patch against Busybox which adds an optional configuration item to ignore all mount options beginning with "x-". An additional verbose option has also been added to enable the ability to report that the mount flags have been ignored, rather than silently ignoring them. This is a requirement for a customer project, where we are limited to using Busybox (due to coreutils' GPL-3.0 licence) but would also require using Snaps like checkbox for testing and verification. This was posted on the Busybox mailing list a few months ago (http://lists.busybox.net/pipermail/busybox/2023-March/090202.html) but patch acceptance there seems to take quite a long time, and we need this for the customer. A PPA containing the patched Busybox version is available on the project's Launchpad team: https://launchpad.net/~nemos- team/+archive/ubuntu/ppa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2022927/+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 2045033] Re: Merge rsyslog 8.2312.0-1 from Debian
Unsubscribing sponsors, since there are merge conflicts. ** Merge proposal linked: https://code.launchpad.net/~xypron/ubuntu/+source/rsyslog/+git/rsyslog/+merge/457541 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2045033 Title: Merge rsyslog 8.2312.0-1 from Debian Status in rsyslog package in Ubuntu: New Bug description: Debian has released rsyslog 8.2310.0-4. Merge it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2045033/+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 2019940] Re: Directly manipulating NetworkManager keyfiles
I patched this upstream in Calamares a month or two ago, and it made it into the 3.3.0 tag, which Lubuntu now has. Calamares will support both, it just now *also* supports Netplan. (If the NM config doesn't exist, no harm no foul no error.) ** Changed in: calamares (Ubuntu) Importance: Undecided => Medium ** Changed in: calamares (Ubuntu) Status: New => Fix Released ** Changed in: calamares (Ubuntu) Milestone: None => ubuntu-23.11 ** Changed in: calamares (Ubuntu) Assignee: (unassigned) => Simon Quigley (tsimonq2) -- 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/2019940 Title: Directly manipulating NetworkManager keyfiles Status in augeas package in Ubuntu: New Status in calamares package in Ubuntu: Fix Released Status in cloud-init package in Ubuntu: Invalid Status in cruft package in Ubuntu: Won't Fix Status in cruft-ng package in Ubuntu: Fix Released Status in dracut package in Ubuntu: New Status in forensic-artifacts package in Ubuntu: New Status in guestfs-tools package in Ubuntu: New Status in guix package in Ubuntu: New Status in ltsp package in Ubuntu: Invalid Status in netcfg package in Ubuntu: Won't Fix Status in netplan.io package in Ubuntu: Invalid Status in network-manager package in Ubuntu: New Status in refpolicy package in Ubuntu: New Status in sosreport package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: New Status in uhd package in Ubuntu: New Status in vagrant package in Ubuntu: New Bug description: The affected packages can manipulate NetworkManager keyfiles directly on disk, which might not be appropriate anymore on Ubuntu, since the Netplan integration was enabled in NetworkManager (starting with Mantic), migrating any keyfile configuration from /etc/NetworkManager/system-connections/*[.nmconnection] to /etc/netplan/90-NM-*.yaml See Netplan's documentation for how connections are handled: https://netplan.readthedocs.io/en/latest/netplan-everywhere/ PS: Packages were queried using: https://codesearch.debian.net/search?q=%2Fsystem-connections&literal=1&perpkg=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/2019940/+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 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies
** Changed in: lubuntu-update-notifier (Ubuntu) Importance: Undecided => Medium ** Changed in: lubuntu-update-notifier (Ubuntu) Status: New => Confirmed ** Changed in: lubuntu-update-notifier (Ubuntu) Milestone: None => ubuntu-24.04-feature-freeze ** Changed in: lubuntu-update-notifier (Ubuntu) Assignee: (unassigned) => Aaron Rainbolt (arraybolt3) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1673258 Title: Remove aptdaemon and drop or port its reverse-dependencies Status in aptdaemon package in Ubuntu: New Status in apturl package in Ubuntu: New Status in dell-recovery package in Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in language-selector package in Ubuntu: New Status in lubuntu-software-center package in Ubuntu: Fix Released Status in lubuntu-update-notifier package in Ubuntu: Confirmed Status in mythbuntu-control-centre package in Ubuntu: Fix Released Status in oem-config package in Ubuntu: New Status in sessioninstaller package in Ubuntu: Fix Released Status in software-properties package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: Fix Released Status in ubuntu-mate-welcome package in Ubuntu: Opinion Status in update-manager package in Ubuntu: New Status in update-notifier package in Ubuntu: New Status in zeroinstall-injector package in Ubuntu: Fix Released Bug description: aptdaemon is abandoned and unmaintained. It has already been dropped from Debian, but there are several reverse dependencies keeping it in Ubuntu. I will add bug tasks for each of those dependencies, which should be ported or dropped themselves. Then we can get rid of aptdaemon too. See this mailing list thread for more details: https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html https://github.com/ubuntu-mate/ubuntu-mate-welcome/issues/48 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1673258/+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 2047008] Re: [SRU] Add Telit FN990 compositions
Uploaded with a changelog tweak. It looks like there is precedent for this, but it's in the SRU team's hands now. DEP-3 patch headers next time? ;) ** Also affects: modemmanager (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: modemmanager (Ubuntu) Status: New => Fix Released ** Changed in: modemmanager (Ubuntu Jammy) Status: New => In Progress ** Changed in: modemmanager (Ubuntu) Importance: Undecided => High ** Changed in: modemmanager (Ubuntu Jammy) Importance: Undecided => High ** Changed in: modemmanager (Ubuntu Jammy) Assignee: (unassigned) => Laider Lai (laiderlai) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2047008 Title: [SRU] Add Telit FN990 compositions Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: In Progress Bug description: [SRU] Add Telit FN990 compositions [ Impact ] The modemmanager v1.20.0 doesn't have Telit FN990 compositions. It works with compatibility mode. (lp: #2046699) [ Test Plan ] Under Jammy environment, check modemmanager can identify Telit FN990 modem correctly. [ Where problems could occur ] The Telit FN990 compositions is upstreamed to modemmanager v1.20.6 https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b68a1bb8474991a72cf988e8e24ba6549f1cf9c2 Noble and Mantic already working with modemmanager v1.20.6. The target platform modem function works well on Mantic. The change parts just only add VID/PIDs for Telit's FN990 modems under the Telit plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2047008/+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 2047705] Re: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration
** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Critical ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed ** Tags added: rls-nn-incoming -- 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/2047705 Title: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Lubuntu uses Qt as the primary framework for most of the apps we ship. However, some functionality we ship in Lubuntu doesn't have a Qt application that provides that functionality, so we have some GTK3 apps that we ship as well. Starting in Lubuntu 24.04, we are adding and enabling the breeze-gtk-theme package, providing more uniform theming between Qt and GTK apps on Lubuntu. However, this bug makes this impossible. As we do not ship xsettingsd, but instead use the XDG specification for shipping configuration, we are attempting to place the default configuration files for GTK2 and GTK3 theming in /etc/xdg/xdg- Lubuntu/gtk-2.0/gtkrc and /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini. This solutions works for GTK2 apps, however GTK3 apps silently ignore the vendored configuration file and are using a different theme. As it turns out, this is because the /etc directory is given higher priority than /etc/xdg/xdg-Lubuntu when searching for XDG configuration files, and as it happens, libgtk-3-0 ships a /etc/gtk-3.0/settings.ini file that sets Yaru as the default theme. GTK3 applications end up selecting this configuration file rather than /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini. /etc/gtk-3.0 is, I would argue, *not* a place where GTK3's settings.ini file should go, as it makes it difficult for flavors who rely on XDG configuration to override it without risking a file conflict. (Technically I guess a flavor package *could* use dpkg- divert to simply "get rid of" the /etc/gtk-3.0/settings.ini file, but that seems like the wrong way to approach this.) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libgtk-3-0 3.24.38-5ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Fri Dec 29 10:08:23 2023 InstallationDate: Installed on 2023-10-22 (69 days ago) InstallationMedia: Lubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) 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/2047705/+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 2047705] Re: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration
** Also affects: lxqt-session (Ubuntu) Importance: Undecided Status: New ** Changed in: lxqt-session (Ubuntu) Status: New => In Progress ** Changed in: lxqt-session (Ubuntu) Importance: Undecided => High ** Changed in: lxqt-session (Ubuntu) Assignee: (unassigned) => Simon Quigley (tsimonq2) -- 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/2047705 Title: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration Status in gtk+3.0 package in Ubuntu: Confirmed Status in lxqt-session package in Ubuntu: In Progress Bug description: Lubuntu uses Qt as the primary framework for most of the apps we ship. However, some functionality we ship in Lubuntu doesn't have a Qt application that provides that functionality, so we have some GTK3 apps that we ship as well. Starting in Lubuntu 24.04, we are adding and enabling the breeze-gtk-theme package, providing more uniform theming between Qt and GTK apps on Lubuntu. However, this bug makes this impossible. As we do not ship xsettingsd, but instead use the XDG specification for shipping configuration, we are attempting to place the default configuration files for GTK2 and GTK3 theming in /etc/xdg/xdg- Lubuntu/gtk-2.0/gtkrc and /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini. This solutions works for GTK2 apps, however GTK3 apps silently ignore the vendored configuration file and are using a different theme. As it turns out, this is because the /etc directory is given higher priority than /etc/xdg/xdg-Lubuntu when searching for XDG configuration files, and as it happens, libgtk-3-0 ships a /etc/gtk-3.0/settings.ini file that sets Yaru as the default theme. GTK3 applications end up selecting this configuration file rather than /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini. /etc/gtk-3.0 is, I would argue, *not* a place where GTK3's settings.ini file should go, as it makes it difficult for flavors who rely on XDG configuration to override it without risking a file conflict. (Technically I guess a flavor package *could* use dpkg- divert to simply "get rid of" the /etc/gtk-3.0/settings.ini file, but that seems like the wrong way to approach this.) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libgtk-3-0 3.24.38-5ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Fri Dec 29 10:08:23 2023 InstallationDate: Installed on 2023-10-22 (69 days ago) InstallationMedia: Lubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) 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/2047705/+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 2047705] Re: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration
A bug still exists here. GTK as a standalone package should not set Yaru as a default, especially if it doesn't declare it as a dependency. lxqt-session was simply a workaround. The Ubuntu Desktop Team needs to move this to their default settings package, and adjust GTK to appropriately read $XDG_CONFIG_DIRS for the appropriate configuration. -- 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/2047705 Title: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration Status in gtk+3.0 package in Ubuntu: Confirmed Status in lxqt-session package in Ubuntu: Fix Released Bug description: Lubuntu uses Qt as the primary framework for most of the apps we ship. However, some functionality we ship in Lubuntu doesn't have a Qt application that provides that functionality, so we have some GTK3 apps that we ship as well. Starting in Lubuntu 24.04, we are adding and enabling the breeze-gtk-theme package, providing more uniform theming between Qt and GTK apps on Lubuntu. However, this bug makes this impossible. As we do not ship xsettingsd, but instead use the XDG specification for shipping configuration, we are attempting to place the default configuration files for GTK2 and GTK3 theming in /etc/xdg/xdg- Lubuntu/gtk-2.0/gtkrc and /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini. This solutions works for GTK2 apps, however GTK3 apps silently ignore the vendored configuration file and are using a different theme. As it turns out, this is because the /etc directory is given higher priority than /etc/xdg/xdg-Lubuntu when searching for XDG configuration files, and as it happens, libgtk-3-0 ships a /etc/gtk-3.0/settings.ini file that sets Yaru as the default theme. GTK3 applications end up selecting this configuration file rather than /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini. /etc/gtk-3.0 is, I would argue, *not* a place where GTK3's settings.ini file should go, as it makes it difficult for flavors who rely on XDG configuration to override it without risking a file conflict. (Technically I guess a flavor package *could* use dpkg- divert to simply "get rid of" the /etc/gtk-3.0/settings.ini file, but that seems like the wrong way to approach this.) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libgtk-3-0 3.24.38-5ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Fri Dec 29 10:08:23 2023 InstallationDate: Installed on 2023-10-22 (69 days ago) InstallationMedia: Lubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) 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/2047705/+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 2047780] Re: BlueZ release 5.71
I very much dislike reviewing packages this way. For a package to be in the sponsorship queue, it needs to have a debdiff, not a debian.tar.xz. I understand that it's a new upstream release, but that does not excuse the need for a debdiff, even if you *also* include these files. I'm uploading this as a courtesy to you and the Desktop Team. Please, don't do it like this again, as I will reject it. ** Changed in: bluez (Ubuntu) Status: In Progress => Fix Committed -- 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/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71
> 34174 lines in this case is not plausibly reviewable. I typically use filterdiff to get the packaging changes, and review specific source files as necessary (including copyright changes in the diff, which can be important, even if you're just using a script for it). Thanks for your help here. I apologize for any undue stress. I will review this in the morning, unless someone else would like the opportunity to fix this sooner. -- 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/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71
Daniel, if you'd like to iterate on this (a debdiff for an ubuntu2 upload), it would be appreciated. If you don't have the time, say the word, this looks like a simple fix. ...on everything but i386. What's up with that? -- 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/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71
The reason I essentially blindsponsored this was out of faith and courtesy for the Desktop Team. Lubuntu does similar things, but we have a merge party from Debian once a cycle. If your response would be "we don't follow Debian," *I get it*, but once or twice a cycle a merge should really be looked at. I'm hoping Daniel, Jeremy, and Sebastien can help get this solved for us. Respectfully, permissiveness will not be present in future uploads. -- 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/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71
Rik mentioned a common mistake that I've been trying harder to catch (but didn't in this case, to my great frustration)... If we're doing a merge and an orig tarball already exists in Debian, always always ALWAYS grab that one instead of using uscan or finding the tarball yourself. It breaks tooling otherwise. -- 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/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71
This is now blocking a Lubuntu feature goal. I tested this locally with my bluetooth earbuds, and have been streaming audio with no problems. Uploaded Gianfranco's packaging with some minor tweaks. Please, we *need* to merge this from Debian *this* cycle. The Security Team will NOT be happy when they have to patch this. E: bluez: depends-on-obsolete-package Depends: lsb-base W: bluez source: illegal-runtime-test-name bluez_response [debian/tests/control:1] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:11] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:14] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:21] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:25] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:28] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:31] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:5] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:11] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:14] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:21] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:28] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:32] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:35] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:38] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:5] W: bluez: no-manual-page [usr/bin/avinfo] W: bluez-meshd: no-manual-page [usr/bin/mesh-cfgclient] W: bluez-meshd: no-manual-page [usr/bin/meshctl] W: bluez-tests: no-manual-page [usr/bin/b1ee] W: bluez-tests: no-manual-page [usr/bin/bnep-tester] W: bluez-tests: no-manual-page [usr/bin/btvirt] W: bluez-tests: no-manual-page [usr/bin/gap-tester] W: bluez-tests: no-manual-page [usr/bin/hci-tester] W: bluez-tests: no-manual-page [usr/bin/hfp] W: bluez-tests: no-manual-page [usr/bin/ioctl-tester] W: bluez-tests: no-manual-page [usr/bin/iso-tester] W: bluez-tests: no-manual-page [usr/bin/l2cap-tester] W: bluez-tests: no-manual-page [usr/bin/mesh-tester] W: bluez-tests: no-manual-page [usr/bin/mgmt-tester] W: bluez-tests: no-manual-page [usr/bin/rfcomm-tester] W: bluez-tests: no-manual-page [usr/bin/sco-tester] W: bluez-tests: no-manual-page [usr/bin/smp-tester] W: bluez-tests: no-manual-page [usr/bin/userchan-tester] W: bluez: systemd-service-file-refers-to-unusual-wantedby-target bluetooth.target [usr/lib/systemd/system/bluetooth.service] W: bluez-meshd: systemd-service-file-refers-to-unusual-wantedby-target bluetooth.target [usr/lib/systemd/system/bluetooth-mesh.service] W: bluez: unusual-interpreter /usr/bin/python [usr/share/apport/package-hooks/source_bluez.py] W: bluez source: useless-autoreconf-build-depends (does not need to satisfy autotools-dev:any) W: bluez source: useless-autoreconf-build-depends (does not need to satisfy autotools-dev:any) W: bluez source: useless-autoreconf-build-depends (does not need to satisfy dh-autoreconf:any) I: bluez source: adopted-extended-field (in section for source) XS-Testsuite [debian/control:28] I: bluez source: adopted-extended-field (in section for source) XSBC-Original-Maintainer [debian/control:5] I: bluez: conflicts-with-version bluez-audio (<= 3.36-3) I: bluez: conflicts-with-version bluez-utils (<= 3.36-3) I: libbluetooth-dev: conflicts-with-version libsdp2-dev (<= 1.5.2) I: libbluetooth3: conflicts-with-version libsdp2 (<= 1.5-2) I: libbluetooth-dev: file-references-package-build-path [usr/lib/x86_64-linux-gnu/bluetooth/plugins/sixaxis.a] I: bluez source: out-of-date-standards-version 3.9.6 (released 2014-09-17) (current is 4.6.2) I: bluez: package-supports-alternative-init-but-no-init.d-script [usr/lib/systemd/system/bluetooth.service] I: bluez-meshd: package-supports-alternative-init-but-no-init.d-script [usr/lib/systemd/system/bluetooth-mesh.service] I: bluez: spare-manual-page [usr/share/man/man1/hid2hci.1.gz] I: bluez: spare-manual-page [usr/share/man/man1/mpris-proxy.1.gz] I: bluez: spelling-error-in-binary Falg Flag [usr/bin/btmon] I: bluez: spelling-error-in-binary Igoring Ignoring [usr/lib/bluetooth/bluetoothd] I: bluez: spelling-error-in-binary Refrence Reference [usr/bin/bluetoothctl] I: bluez: spelling-error-in-binary Refrence Reference [usr/bin/btmon] I: bluez: spelling-error-in-binary Refrence Refe
[Touch-packages] [Bug 2047780] Re: BlueZ release 5.71
Following the dependency chain through to the cause for the i386 builds, binfmt-support should be added to the i386 allowlist. This may be a bug in evolution-data-server in the case libebook-contacts-1.2-4 can build without libphonenumber8-protobuf32 - for now, blanket-disabling that dependency in bluez's debian/control. ...Debian doesn't even have this build dependency in their bluez packaging, why do we have it in ours? If we need to have it, why isn't that a bug in Debian, and why aren't we working with the Debian Bluetooth maintainers to fix this? -- 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/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71
> In other words, asking an Archive Admin to build binfmt-support on i386. I have stopped short of this so far because I'm entirely unsure if we still need that build dependency in the first place. Debian doesn't have it, and I'm not sure I see rationale on our end for it. There is probably something I'm missing, but I don't have the justification myself to make such a request. -- 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/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047982] Re: Highlighting of patches offers insufficient contrast
Is there any terminal in which the default is actually readable? ** Changed in: vim (Ubuntu) Assignee: (unassigned) => Simon Quigley (tsimonq2) ** Changed in: vim (Ubuntu) Milestone: None => ubuntu-24.04-feature-freeze ** Changed in: vim (Ubuntu) Importance: Undecided => Medium -- 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/2047982 Title: Highlighting of patches offers insufficient contrast Status in vim package in Ubuntu: Confirmed Bug description: With vim 2:9.0.2189-1ubuntu1 the coloring of patches has been changed. The result is that in konsole patches have become illegible. See appendix. Deleted lines have foreground cyan #18b2b2 and background light blue #7f7fff. Kind of blue on blue. Please, provide sane color defaults. The previous release used bright white on black for deleted lines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2047982/+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 2047780] Re: BlueZ release 5.71
Daniel, I don't want you to feel burned over this. That wiki page does seem quite rational, and I appreciate that you linked it. I'm reading some mixed feelings, so let me be clear: thank you for the work you *are* able to put into this. Both Gianfranco and I are Ubuntu Core Developers but are also Debian Developers. An expectation of working with Debian is #3 of the Social Contract, "Don't Hide Problems" https://www.debian.org/social_contract If Debian has problems in their packaging that do exist, please file a bug. If the maintainer is non-responsive in Debian, there is a process for non-maintainer uploads (and I would personally help you with this). My point of disagreement is not how we are addressing the Ubuntu uploads as much as how we are working with Debian to fix them. If the Debian team is non-collaborative, that should be addressed with the appropriate governance board. Either way, there should be a clear diff, whether the community has to help or not. That being said, considerateness is part of Ubuntu's CoC. I will push my commits there in the morning. I do apologize again for any undue stress. I would rather address this head on, because it means a better Bluetooth package for our users. Jeremy, the reason evolution-data-server has uninstallable binaries is because of the binfmt-supoort i386 allowlist issue at hand. Please confirm whether you have a customer story that will be impacted by this, or if we think a user will seriously need this support on i386 in 2024. I may be an Ubuntu Core Developer, but I respect that it's not my call alone to make, and the last thing I want to do is regress something for a customer. That's why I'm being up front about these issues. -- 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/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71
** Changed in: bluez (Ubuntu) Status: Fix Released => In Progress ** Summary changed: - BlueZ release 5.71 + BlueZ release 5.71 and merge from Debian ** Changed in: bluez (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => Simon Quigley (tsimonq2) -- 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/2047780 Title: BlueZ release 5.71 and merge from Debian Status in bluez package in Ubuntu: In Progress Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71 and merge from Debian
At first I was just going to say, ell-dev isn't built on i386 and it's not arch:all, of course it will need an i386 allowlist entry! However, this is the output I'm getting: ``` $ check-mir Checking support status of build dependencies... * debhelper-compat does not exist (pure virtual?) * libell-dev binary and source package is in universe * check binary and source package is in universe Checking support status of binary dependencies... * default-dbus-system-bus does not exist (pure virtual?) ... alternative dbus-system-bus does not exist (pure virtual?) Please check https://wiki.ubuntu.com/MainInclusionProcess if this source package needs to get into in main/restricted, or reconsider if the package really needs above dependencies. ``` I'm going to fix check-mir itself so it ignores debhelper-compat (that is certainly a false flag since debhelper is in main, and I don't want to see anyone waste time on this red herring), `libell-dev` and `check` are valid points. Both of those seem like reasonably small libraries that could be MIRed, especially ell for embedded devices. That being said, we did not have these dependencies before, so this is much lower on my priority list. I would highly encourage someone to beat me to it. That being said, I've been listening to music with no issue with the updated bluez, which is what I would expect to be the baseline for a "working" bluez. The only quirk I noticed is that despite my device (Beats Flex) being set to autoconnect, I needed to manually connect (to the already saved device). Connected promptly, no stuttering issues (from YouTube Music/Firefox Nightly snap), audio is as good/loud as I would expect it to be, and volume control works smoothly. I'm not noticing anything particularly different on the blueman configuration front. tl;dr: Uploaded Gianfranco's diff to Noble with slight modifications. This will need to go through binary NEW. -- 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/2047780 Title: BlueZ release 5.71 and merge from Debian Status in bluez package in Ubuntu: In Progress Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71
I'm pretty shocked, I ran a local sbuild with this and yet it still FTBFS. Doing an ubuntu2 upload as a fixup. I would think that because we use the published tarball and not the upstream source like Debian does, that would affect our ability to ship the -test package. Something's up with my local setup. I'll figure it out, fix it, and allow us to move forward here. -- 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/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Released Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71
> Please also remember to commit proposed changes to https://git.launchpad.net/~bluetooth/bluez Force pushing my local commits over, sorry not sorry. :) -- 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/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Released Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71
> Simon, ell already has a recent approved MIR LP: #1971738 Er, the binary packages in question don't. -- 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/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Released Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047982] Re: Highlighting of patches offers insufficient contrast
https://github.com/vim/vim/pull/13825 I will test this first in Debian, upload it there, then do a merge. ** Changed in: vim (Ubuntu) Status: Confirmed => In Progress -- 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/2047982 Title: Highlighting of patches offers insufficient contrast Status in vim package in Ubuntu: In Progress Bug description: With vim 2:9.0.2189-1ubuntu1 the coloring of patches has been changed. The result is that in konsole patches have become illegible. See appendix. Deleted lines have foreground cyan #18b2b2 and background light blue #7f7fff. Kind of blue on blue. Please, provide sane color defaults. The previous release used bright white on black for deleted lines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2047982/+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 2047780] Re: BlueZ release 5.71
It looks like I was overly strict with the MIR compliance, which sort of balances out this bug as a whole. :) After it migrates, Gianfranco or myself will try reverting ubuntu2 to see if we can push those two packages forward. -- 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/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Released Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047982] Re: Highlighting of patches offers insufficient contrast
** Changed in: vim (Ubuntu) Status: In Progress => Fix Committed -- 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/2047982 Title: Highlighting of patches offers insufficient contrast Status in vim package in Ubuntu: Fix Committed Bug description: With vim 2:9.0.2189-1ubuntu1 the coloring of patches has been changed. The result is that in konsole patches have become illegible. See appendix. Deleted lines have foreground cyan #18b2b2 and background light blue #7f7fff. Kind of blue on blue. Please, provide sane color defaults. The previous release used bright white on black for deleted lines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2047982/+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 2049318] Re: free(): double free detected in tcache 2
** Also affects: iptables (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/2049318 Title: free(): double free detected in tcache 2 Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Jammy: In Progress Bug description: nftables is being used successfully with no difficulty. Running iptables on my node receives a crash: $ sudo iptables -nL free(): double free detected in tcache 2 Aborted (core dumped) without sudo # iptables -nL free(): double free detected in tcache 2 Aborted (core dumped) This bug is known and was fixed in version 1.8.8 of iptables https://git.netfilter.org/iptables/commit/?id=4318961230bce82958df82b57f1796143bf2f421 1) The release of Ubuntu $ lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 2) The version of the package $ apt info iptables Package: iptables Version: 1.8.7-1ubuntu5.1 3) What you expected to happen not to crash with valid, working nftables rules 4) What happened instead crash A plausible workaround could be a backport of iptables 1.8.9 from mantic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: iptables 1.8.7-1ubuntu5.1 ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131 Uname: Linux 5.15.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Sun Jan 14 20:36:59 2024 InstallationDate: Installed on 2021-11-23 (782 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: iptables UpgradeStatus: Upgraded to jammy on 2023-04-30 (259 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/2049318/+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 2040011] Re: [SRU] Ensure supported codenames are accurate
** Changed in: vim (Ubuntu) Status: In Progress => Fix Released -- 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/2040011 Title: [SRU] Ensure supported codenames are accurate Status in vim package in Ubuntu: Fix Released Status in vim source package in Focal: In Progress Status in vim source package in Jammy: In Progress Status in vim source package in Lunar: In Progress Status in vim source package in Mantic: In Progress Bug description: In several stable releases of Ubuntu, Vim has information regarding releases that are outdated. It would be optimal for Vim to grab this data from distro-info-data (or similar), but unfortunately that is not the case. Therefore, the list needs to be updated. There is a minimal regression potential here; Vim simply reads a statically-set Perl array to determine if the release in the changelog and sources.list is supported or not. Any regression would present itself in external tooling that detects text highlighting, which is not a case I think we support in Ubuntu. A simple way to test this update is to download a package from the Lunar archive, and open the changelog with Vim. Instead of the changelog release (e.g. "noble") showing as red, it should show as blue. I would also suggest editing sources.list, to ensure e.g. Eoan shows as EOL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2040011/+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 2049352] Re: Package BlueZ 5.72 for Noble
This was missing a build dependency on python3-pygments (which is in Main), I added it. Testing well with my Beats Flex, YouTube Music with the Firefox Nightly snap. I can adjust the latency offset with no issue, and blueman DTRT with connecting and disconnecting. Popped open journalctl and syslog, no errors presented on either front. As usual, here are the Lintian flags raised (that I don't plan on blocking on, but you should at least be aware of.) Regardless, great work, thank you! W: bluez source: illegal-runtime-test-name bluez_response [debian/tests/control:1] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:11] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:14] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:21] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:25] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:28] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:31] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:5] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:16] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:22] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:25] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:32] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:39] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:43] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:46] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:49] W: bluez-test-tools: no-manual-page [usr/bin/hfp] W: bluez-test-tools: no-manual-page [usr/bin/ioctl-tester] W: bluez-test-tools: no-manual-page [usr/bin/iso-tester] W: bluez-test-tools: no-manual-page [usr/bin/mesh-tester] W: bluez source: superfluous-file-pattern obexd/plugins/messages-tracker.c [debian/copyright:632] W: bluez source: superfluous-file-pattern obexd/plugins/syncevolution.c [debian/copyright:511] W: bluez: systemd-service-file-refers-to-unusual-wantedby-target bluetooth.target [usr/lib/systemd/system/bluetooth.service] W: bluez-meshd: systemd-service-file-refers-to-unusual-wantedby-target bluetooth.target [usr/lib/systemd/system/bluetooth-mesh.service] W: bluez: unusual-interpreter /usr/bin/python [usr/share/apport/package-hooks/source_bluez.py] I: bluez source: adopted-extended-field (in section for source) XSBC-Original-Maintainer [debian/control:3]
[Touch-packages] [Bug 2049352] Re: Package BlueZ 5.72 for Noble
** Changed in: bluez (Ubuntu) Status: In Progress => Fix Committed -- 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/2049352 Title: Package BlueZ 5.72 for Noble Status in bluez package in Ubuntu: Fix Committed Bug description: ver 5.72: Fix issue with BAP and handling stream IO linking. Fix issue with BAP and setup of multiple streams per endpoint. Fix issue with AVDTP and potential incorrect transaction label. Fix issue with A2DP and handling crash on suspend. Fix issue with GATT database and an invalid pointer. Add support for AICS service. https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.72.tar.xz https://git.kernel.org/pub/scm/bluetooth/bluez.git/tag/?h=5.72 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049352/+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 2049885] Re: Merge console-setup (1.223) from Debian
** Patch added: "delta-delta.patch" https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/2049885/+attachment/5741436/+files/delta-delta.patch ** Changed in: console-setup (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/2049885 Title: Merge console-setup (1.223) from Debian Status in console-setup package in Ubuntu: Fix Committed Bug description: In Debian console-setup (1.223) is available. It should be merged into Noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/2049885/+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 1996087] [NEW] Ensure supported codenames are accurate
Public bug reported:
In several stable releases of Ubuntu, Vim has information regarding
releases that are outdated. It would be optimal for Vim to grab this
data from distro-info-data (or similar), but unfortunately that is not
the case. Therefore, the list needs to be updated.
There is a minimal regression potential here; Vim simply reads a
statically-set Perl array to determine if the release in the changelog
is supported or not. Any regression would present itself in external
tooling that detects text highlighting, which is not a case I think we
support in Ubuntu.
A simple way to test this update is to download a package from the Lunar
archive, and open the changelog with Vim. Instead of the changelog
release (e.g. "lunar") showing as red, it should show as blue.
** Affects: vim (Ubuntu)
Importance: Undecided
Assignee: Simon Quigley (tsimonq2)
Status: Fix Committed
** Affects: vim (Ubuntu Focal)
Importance: Undecided
Assignee: Simon Quigley (tsimonq2)
Status: Confirmed
** Affects: vim (Ubuntu Jammy)
Importance: Undecided
Assignee: Simon Quigley (tsimonq2)
Status: Confirmed
** Affects: vim (Ubuntu Kinetic)
Importance: Undecided
Assignee: Simon Quigley (tsimonq2)
Status: Confirmed
** Affects: vim (Ubuntu Lunar)
Importance: Undecided
Assignee: Simon Quigley (tsimonq2)
Status: Fix Committed
** Also affects: vim (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: vim (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: vim (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: vim (Ubuntu Lunar)
Importance: Undecided
Status: New
** Changed in: vim (Ubuntu Lunar)
Status: New => Confirmed
** Changed in: vim (Ubuntu Lunar)
Status: Confirmed => Fix Committed
** Changed in: vim (Ubuntu Kinetic)
Status: New => Confirmed
** Changed in: vim (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: vim (Ubuntu Focal)
Status: New => Confirmed
** Changed in: vim (Ubuntu Focal)
Assignee: (unassigned) => Simon Quigley (tsimonq2)
** Changed in: vim (Ubuntu Jammy)
Assignee: (unassigned) => Simon Quigley (tsimonq2)
** Changed in: vim (Ubuntu Kinetic)
Assignee: (unassigned) => Simon Quigley (tsimonq2)
** Changed in: vim (Ubuntu Lunar)
Assignee: (unassigned) => Simon Quigley (tsimonq2)
--
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/1996087
Title:
Ensure supported codenames are accurate
Status in vim package in Ubuntu:
Fix Committed
Status in vim source package in Focal:
Confirmed
Status in vim source package in Jammy:
Confirmed
Status in vim source package in Kinetic:
Confirmed
Status in vim source package in Lunar:
Fix Committed
Bug description:
In several stable releases of Ubuntu, Vim has information regarding
releases that are outdated. It would be optimal for Vim to grab this
data from distro-info-data (or similar), but unfortunately that is not
the case. Therefore, the list needs to be updated.
There is a minimal regression potential here; Vim simply reads a
statically-set Perl array to determine if the release in the changelog
is supported or not. Any regression would present itself in external
tooling that detects text highlighting, which is not a case I think we
support in Ubuntu.
A simple way to test this update is to download a package from the
Lunar archive, and open the changelog with Vim. Instead of the
changelog release (e.g. "lunar") showing as red, it should show as
blue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1996087/+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 1996087] Re: Ensure supported codenames are accurate
** Description changed: In several stable releases of Ubuntu, Vim has information regarding releases that are outdated. It would be optimal for Vim to grab this data from distro-info-data (or similar), but unfortunately that is not the case. Therefore, the list needs to be updated. There is a minimal regression potential here; Vim simply reads a statically-set Perl array to determine if the release in the changelog - is supported or not. Any regression would present itself in external - tooling that detects text highlighting, which is not a case I think we - support in Ubuntu. + and sources.list is supported or not. Any regression would present + itself in external tooling that detects text highlighting, which is not + a case I think we support in Ubuntu. A simple way to test this update is to download a package from the Lunar archive, and open the changelog with Vim. Instead of the changelog - release (e.g. "lunar") showing as red, it should show as blue. + release (e.g. "lunar") showing as red, it should show as blue. I would + also suggest editing sources.list, to ensure e.g. Eoan shows as EOL. -- 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/1996087 Title: Ensure supported codenames are accurate Status in vim package in Ubuntu: Fix Committed Status in vim source package in Focal: Confirmed Status in vim source package in Jammy: Confirmed Status in vim source package in Kinetic: Confirmed Status in vim source package in Lunar: Fix Committed Bug description: In several stable releases of Ubuntu, Vim has information regarding releases that are outdated. It would be optimal for Vim to grab this data from distro-info-data (or similar), but unfortunately that is not the case. Therefore, the list needs to be updated. There is a minimal regression potential here; Vim simply reads a statically-set Perl array to determine if the release in the changelog and sources.list is supported or not. Any regression would present itself in external tooling that detects text highlighting, which is not a case I think we support in Ubuntu. A simple way to test this update is to download a package from the Lunar archive, and open the changelog with Vim. Instead of the changelog release (e.g. "lunar") showing as red, it should show as blue. I would also suggest editing sources.list, to ensure e.g. Eoan shows as EOL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1996087/+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 2028769] Re: [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal in Jammy
I'm just generally curious, does debootstrap function differently with/without this patch? I'd imagine it either goes off the task, or a level lower than the metapackages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2028769 Title: [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal in Jammy Status in ubuntu-meta package in Ubuntu: New Bug description: [ Impact ] Without packages ubuntu-desktop, ubuntu-desktop-minimal it is unnecessarily difficult to setup the Ubuntu desktop on systems like the SiFive HiFive Unmatched. All dependent packages are available. We just need to add the riscv64 architecture in debian/control. [ Test Plan ] Reproducing the issue: * Check that the packages ubuntu-desktop, ubuntu-desktop-minimal are not available for riscv64 in the archive. Testing: * Install Ubuntu Jammy using the live installer on the SiFive HiFive Unmatched board. * Install package ubuntu-desktop-minimal. * Install package ubuntu-desktop. * Reboot * Login * Check that you have a function desktop by opening a preinstalled application. [ Where problems could occur ] * The packages might not be installable due to missing dependencies. * The Gnome desktop might fail. [ Other Info ] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2028769/+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 2028769] Re: [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal in Jammy
Ah, right. Debootstrap is more low-level, thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2028769 Title: [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal in Jammy Status in ubuntu-meta package in Ubuntu: New Bug description: [ Impact ] Without packages ubuntu-desktop, ubuntu-desktop-minimal it is unnecessarily difficult to setup the Ubuntu desktop on systems like the SiFive HiFive Unmatched. All dependent packages are available. We just need to add the riscv64 architecture in debian/control. [ Test Plan ] Reproducing the issue: * Check that the packages ubuntu-desktop, ubuntu-desktop-minimal are not available for riscv64 in the archive. Testing: * Install Ubuntu Jammy using the live installer on the SiFive HiFive Unmatched board. * Install package ubuntu-desktop-minimal. * Install package ubuntu-desktop. * Reboot * Login * Check that you have a function desktop by opening a preinstalled application. [ Where problems could occur ] * The packages might not be installable due to missing dependencies. * The Gnome desktop might fail. [ Other Info ] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2028769/+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 1801439] Re: Unable to add software sources via the software-properties-qt
** Changed in: software-properties (Ubuntu) Assignee: Simon Quigley (tsimonq2) => Hans P Möller (hmollercl) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1801439 Title: Unable to add software sources via the software-properties-qt Status in software-properties package in Ubuntu: Triaged Bug description: Test 1. Start Software-properties. E.g. sudo software-properties-qt 2. Navigate to Other Software (Tab), Add -> Add, to add a PPA 3. Insert the PPA string. E.g. "deb http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu cosmic main " (or even the example repo given in the dialog, which is not a PPA) 4. Click Okay. The software sources list does not contain the new field. Executing in terminal results in the following error message. Traceback (most recent call last):   File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 627, in on_add_clicked self.add_source_from_line(line)   File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 752, in add_source_from_line enable_source_code=enable_source_code)   File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 769, in add_source_from_shortcut worker = self.check_and_add_key_for_whitelisted_shortcut(shortcut)   File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 709, in check_and_add_key_for_whitelisted_shortcut self.options.keyserver)}) AttributeError: type object 'OptionParsed' has no attribute 'keyserver' ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: software-properties-qt 0.96.27 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: LXQt Date: Sat Nov 3 09:59:52 2018 InstallationDate: Installed on 2018-10-19 (14 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1801439/+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 1829805] Re: Lubuntu Eoan Daily Image fails to boot after install on KVM
The bug was only fixed in our Calamares configuration and still needs to be fixed in initramfs-tools. Adjusting bug statuses appropriately and adding the release tag. I'll ping vorlon and xnox on IRC to get their take. ** Also affects: calamares-settings-ubuntu (Ubuntu) Importance: Undecided Status: New ** Changed in: calamares-settings-ubuntu (Ubuntu) Importance: Undecided => Critical ** Changed in: initramfs-tools (Ubuntu) Importance: Critical => High ** Changed in: calamares-settings-ubuntu (Ubuntu) Assignee: (unassigned) => Walter Lapchynski (wxl) ** Changed in: calamares-settings-ubuntu (Ubuntu) Status: New => Fix Released ** Changed in: initramfs-tools (Ubuntu) Status: Fix Released => Triaged ** Changed in: initramfs-tools (Ubuntu) Assignee: Walter Lapchynski (wxl) => (unassigned) ** No longer affects: linux (Ubuntu) ** Tags added: rls-ee-incoming -- 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/1829805 Title: Lubuntu Eoan Daily Image fails to boot after install on KVM Status in calamares-settings-ubuntu package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Triaged Bug description: Context: The live environment appears to function properly and install proceeds as expected with no noticeable errors. Expected results: After a system reboot the virtual machine enters the graphical environment Actual Results: After rebooting the virtual machine a kernel panic error screen appears. I will attempt to attach the screenshot after submitting this bug report. The collected data is from the live environment as the installed environment will not boot. lubuntu@lubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Eoan Ermine (development branch) Release:19.10 Codename: eoan lubuntu@lubuntu:~$ apt-cache policy grub2 grub2: Installed: (none) Candidate: 2.02+dfsg1-12ubuntu2 Version table: 2.02+dfsg1-12ubuntu2 500 500 cdrom://Lubuntu 19.10 _Eoan Ermine_ - Alpha amd64 (20190519) eoan/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.407 CurrentDesktop: LXQt Date: Tue May 21 00:30:39 2019 LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190519) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/1829805/+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 1822380] Re: Thunar right-click menu not expanded
Unsubscribing the sponsors team as there's nothing left to sponsor here. -- 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/1822380 Title: Thunar right-click menu not expanded Status in GTK+: New Status in Thunar File Manager: Fix Released Status in gtk+3.0 package in Ubuntu: Triaged Status in thunar package in Ubuntu: Fix Released Bug description: Submitting this bug report with the SRU template, but hopefully we can go ahead have this uploaded before the final images have been built. [Impact] * The "Create Document" submenu in Thunar does not expand to a usable length. * The submenu is displayed at just a few pixels tall, enough to see menu items as you scroll, but not enough to read any item. * This breaks a standard use case for file managers: creating new files. * The proposed upload fixes the bug by loading the menu items synchronously, making the menu load with the items already populated instead of having to redraw once the items are added. * The patch provided comes from the upstream maintainer. [Test Case] * Open Thunar. * Right click in the blank space (not on an item). * Move the cursor to the "Create Document" menu. * Bug Present: The submenu is displayed but short, and no items are visible. * Bug Resolved: The submenu is displayed, items present in the ~/Templates folder are displayed. [Regression Potential] * Regression potential is minimal: * The modified code affects only the drawing of the submenu items. * The submenu is already ununsable, no items are displayed. * Some limited testing has already been completed: * 2 users confirmed the patch fixes the issue on the upstream bug report. * 2 Xubuntu team members (bluesabre, Unit193) have also confirmed the patch and no regressions. [Original Report] In Thunar, when I right click to create a new file, the menu shows up so small that I can't see the options. I have rebooted and the problem persists. Haven't checked other file managers yet. Running Xubuntu 19.04 (Development Branch), Thunar 1.8.4. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: thunar 1.8.4-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 29 16:41:29 2019 InstallationDate: Installed on 2019-03-29 (0 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) SourcePackage: thunar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1822380/+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 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
Unsubscribing the Sponsors Team as there is no debdiff to sponsor. Poked the Security Team. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs Status in jackd2 package in Ubuntu: New Status in jackd2 package in Debian: New Bug description: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumerating the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multi-threaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+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 1834211] Re: [SRU] gconf FTBFS in Bionic
Before this is sponsored, I would like to see Brian's comment on the other bug addressed; does this need to go to Eoan, any other releases, or Debian? Thanks, and please resubscribe sponsors when this is answered. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1834211 Title: [SRU] gconf FTBFS in Bionic Status in gconf package in Ubuntu: New Bug description: [Impact] Two issues make gconf FTBFS in Bionic: - outdated gtk-doc.make which fails with gtk-doc-tools >= 1.26 - missing dh-python in B-D The debdiff attached below fixes these issues and makes gconf build properly. [Test Case] Just install the needed build dependencies and try to build gconf. It will fail with an error from gtk-doc.make. Second issue: if gtk- doc.make is patched, the build will fail if dh-python isn't installed. [Regression Potential] None, you can't break it more than FTBFS :) [Other Info] Fixes are backported from Cosmic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1834211/+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 1835095] Re: Lubuntu initrd images leaking cryptographic secret when disk encryption is used
** Package changed: initramfs-tools (Ubuntu) => calamares (Ubuntu) ** No longer affects: lubuntu-meta (Ubuntu) -- 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/1835095 Title: Lubuntu initrd images leaking cryptographic secret when disk encryption is used Status in calamares package in Ubuntu: Confirmed Bug description: Hello! I've had a short discussion about this issue on lubuntu irc, and I was asked to open a bug report. Basically I only tested this on lubuntu 19.04 x64 live image on a UEFI system, I haven't tested other ubuntu flavors. Anyway, I was poking around with disk encryption, and I noticed that lubuntu live image uses a graphical installation tool called Calamares. This tool has an option to encrypt the hard disk during installation, and the encryption setup that is used is the newer one with /boot folder as part of the encrypted rootfs. Traditionally the installers used to setup encryption where there is a main LUKS- encrypted rootfs volume on the HDD and a separate unencrypted /boot partition where the grub config files, the kernel and the initrd images reside. Ever since grub2 added support for LUKS several distros have apparently moved to the newer scheme which is very similar to the one that was first described by Pavel Kogan in his blog. A) https://www.pavelkogan.com/2014/05/23/luks-full-disk-encryption/ B) https://www.pavelkogan.com/2015/01/25/linux-mint-encryption/ This new scheme stores the rootfs (including the /boot folder) on a single LUKS-encrypted partition with two keyslots in use. One of the keyslots is normally a passphrase that is used in the first stage by the grub2 EFI image as pre-boot authentication. It serves to decrypt the rootfs, access the contents of /boot and copy the config, kernel and initrd image to RAM. Once done, grub2 then forgets the passphrase and closes the encrypted volume. The system will continue to boot, but at this point the rootfs will now have to be decrypted a second time - this time by the kernel/initrd so it can be mounted. Normally this is the point where the user would be asked to enter a passphrase for the second time, but for convenience reasons (to automate the process) a second LUKS keyslot and a keyfile are used instead. The file /crypto_keyfile.bin is generated during the installation phase. This is the secret keyfile that is used to unlock the other LUKS keyslot and decrypt the rootfs. It is properly protected with owner set to root:root and file permissions 600 (-rw---). Unfortunately the key is not of much use while it resides inside the encrypted volume that it is supposed to decrypt. This is where initramfs-tools comes into play. I believe there is a special hook inside /usr/share/initramfs-tools/hooks that is responsible for copying this crypto_keyfile.bin file into appropriate initrd image. This image that now contains the secret keyfile is copied into RAM during the first decryption stage by the grub2. While the original secret keyfile /crypto_keyfile.bin is protected: $ ls -l / ... -rw--- 1 root root 2048 jul 2 18:34 crypto_keyfile.bin ... $ sha1sum /crypto_keyfile.bin sha1sum: /crypto_keyfille.bin: Permission denied $ sudo sha1sum /crypto_keyfile.bin 7a1c44fd036510cc02e32c094bd16b4a76a7f14c /crypto_keyfile.bin The second copy (the one inside initramfs image) is not: $ ls -l /boot ... -rw-r--r-- 1 root root 68149041 jul 2 18:35 initrd.img-5.0.0-13-generic As you can see, the initramfs images that are generated by mkinitramfs will have the user:group set to root:root, but their access flags will be 644 (-rw-r--r--). This means that any user or even a script that has read access to the file system can read and extract the secret keyfile from an initramfs image. Run as user: $ unmkinitramfs /boot/initrd.img-5.0.0-13-generic /tmp $ sha1sum /tmp/main/crypto_keyfile.bin 7a1c44fd036510cc02e32c094bd16b4a76a7f14c /tmp/main/crypto_keyfile.bin Would there be any adverse effects, if we were to set mkinitramfs (i.e. via a hook) to always set file permissions of initramfs images to 600 whenever this type of disk encryption is used? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1835095/+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 1801439] Re: Unable to add software sources via the software-properties-qt
I'll take this one. ** Changed in: software-properties (Ubuntu) Assignee: (unassigned) => Simon Quigley (tsimonq2) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1801439 Title: Unable to add software sources via the software-properties-qt Status in software-properties package in Ubuntu: Triaged Bug description: Test 1. Start Software-properties. E.g. sudo software-properties-qt 2. Navigate to Other Software (Tab), Add -> Add, to add a PPA 3. Insert the PPA string. E.g. "deb http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu cosmic main " (or even the example repo given in the dialog, which is not a PPA) 4. Click Okay. The software sources list does not contain the new field. Executing in terminal results in the following error message. Traceback (most recent call last): Â Â File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 627, in on_add_clicked self.add_source_from_line(line) Â Â File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 752, in add_source_from_line enable_source_code=enable_source_code) Â Â File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 769, in add_source_from_shortcut worker = self.check_and_add_key_for_whitelisted_shortcut(shortcut) Â Â File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 709, in check_and_add_key_for_whitelisted_shortcut self.options.keyserver)}) AttributeError: type object 'OptionParsed' has no attribute 'keyserver' ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: software-properties-qt 0.96.27 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: LXQt Date: Sat Nov 3 09:59:52 2018 InstallationDate: Installed on 2018-10-19 (14 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1801439/+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 1757915] Re: Please port your package away from Qt 4
** Changed in: zbar (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zbar in Ubuntu. https://bugs.launchpad.net/bugs/1757915 Title: Please port your package away from Qt 4 Status in zbar package in Ubuntu: Fix Released Status in zbar package in Debian: Fix Released Bug description: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zbar/+bug/1757915/+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 1770062] Re: Please merge 2.3.2-1 from Debian Sid
Attached is a debdiff applicable to 2.3.2-1, which is in Sid. ** Patch added: "1-2.3.2-1-to-2.3.2-1ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/slang2/+bug/1770062/+attachment/5136512/+files/1-2.3.2-1-to-2.3.2-1ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to slang2 in Ubuntu. https://bugs.launchpad.net/bugs/1770062 Title: Please merge 2.3.2-1 from Debian Sid Status in slang2 package in Ubuntu: In Progress Bug description: Debian Sid contains a new upstream release. Let's merge it. Changelog entries since the last Ubuntu upload: slang2 (2.3.2-1) unstable; urgency=medium * New upstream release - extended_terminfo.patch now included upstream * Ack old bugs: Closes: #407835, #664075 * Set OBJDIR to src/x32objs on x32. Closes: #890545 -- Alastair McKinstry Mon, 19 Feb 2018 16:59:12 + To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/slang2/+bug/1770062/+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 1770062] [NEW] Please merge 2.3.2-1 from Debian Sid
Public bug reported: Debian Sid contains a new upstream release. Let's merge it. Changelog entries since the last Ubuntu upload: slang2 (2.3.2-1) unstable; urgency=medium * New upstream release - extended_terminfo.patch now included upstream * Ack old bugs: Closes: #407835, #664075 * Set OBJDIR to src/x32objs on x32. Closes: #890545 -- Alastair McKinstry Mon, 19 Feb 2018 16:59:12 + ** Affects: slang2 (Ubuntu) Importance: Wishlist Assignee: Simon Quigley (tsimonq2) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to slang2 in Ubuntu. https://bugs.launchpad.net/bugs/1770062 Title: Please merge 2.3.2-1 from Debian Sid Status in slang2 package in Ubuntu: In Progress Bug description: Debian Sid contains a new upstream release. Let's merge it. Changelog entries since the last Ubuntu upload: slang2 (2.3.2-1) unstable; urgency=medium * New upstream release - extended_terminfo.patch now included upstream * Ack old bugs: Closes: #407835, #664075 * Set OBJDIR to src/x32objs on x32. Closes: #890545 -- Alastair McKinstry Mon, 19 Feb 2018 16:59:12 + To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/slang2/+bug/1770062/+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 1757320] [NEW] Remove Qt 4 from the archive
Public bug reported: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or the whole source package removal) before the 19.04 release. If it is possible to do this by the 18.10 release, please do so. No new packages entering the Ubuntu archive should depend on qt4-x11 or any package which directly or indirectly depends on it. [1] https://wiki.debian.org/Qt4Removal affects ubuntu/acoustid-fingerprinter importance medium affects ubuntu/adwaita-qt importance medium affects ubuntu/akonadi4 importance medium affects ubuntu/alsoft-conf importance medium affects ubuntu/alt-key importance medium affects ubuntu/amarok importance medium affects ubuntu/amora-server importance medium affects ubuntu/ams importance medium affects ubuntu/analitza4 importance medium affects ubuntu/appmenu-qt importance medium affects ubuntu/aseba importance medium affects ubuntu/attal importance medium affects ubuntu/attica importance medium affects ubuntu/auralquiz importance medium affects ubuntu/automoc importance medium affects ubuntu/autopilot-qt importance medium affects ubuntu/avogadro importance medium affects ubuntu/bacula importance medium affects ubuntu/ball importance medium affects ubuntu/baloo importance medium affects ubuntu/basket importance medium affects ubuntu/boats importance medium affects ubuntu/bodega-client importance medium affects ubuntu/bppphyview importance medium affects ubuntu/breeze importance medium affects ubuntu/cagibi importance medium affects ubuntu/cdcat importance medium affects ubuntu/chinese-calendar importance medium affects ubuntu/choreonoid importance medium affects ubuntu/clementine importance medium affects ubuntu/cmtk importance medium affects ubuntu/codelite importance medium affects ubuntu/codequery importance medium affects ubuntu/collatinus importance medium affects ubuntu/colord-kde importance medium affects ubuntu/connectome-workbench importance medium affects ubuntu/cortina importance medium affects ubuntu/cppreference-doc importance medium affects ubuntu/daemonfs importance medium affects ubuntu/dc-qt importance medium affects ubuntu/dee-qt importance medium affects ubuntu/dgedit importance medium affects ubuntu/dhcpcd-ui importance medium affects ubuntu/doomsday importance medium affects ubuntu/dssi importance medium affects ubuntu/enki-aseba importance medium affects ubuntu/eqonomize importance medium affects ubuntu/esperanza importance medium affects ubuntu/fbreader importance medium affects ubuntu/fcitx importance medium affects ubuntu/fcitx-kkc importance medium affects ubuntu/felix-latin importance medium affects ubuntu/flightcrew importance medium affects ubuntu/fmit importance medium affects ubuntu/fraqtive importance medium affects ubuntu/freecad importance medium affects ubuntu/freemat importance medium affects ubuntu/freemedforms-project importance medium affects ubuntu/freeplayer importance medium affects ubuntu/gammaray importance medium affects ubuntu/gebabbel importance medium affects ubuntu/genpo importance medium affects ubuntu/gle-graphics importance medium affects ubuntu/gmic importance medium affects ubuntu/gnash importance medium affects ubuntu/gnudoq importance medium affects ubuntu/grantlee importance medium affects ubuntu/gr-fosphor importance medium affects ubuntu/gr-radar importance medium affects ubuntu/gwenrename importance medium affects ubuntu/hamfax importance medium affects ubuntu/hedgewars importance medium affects ubuntu/heimdall-flash importance medium affects ubuntu/holdingnuts importance medium affects ubuntu/hydrogen importance medium affects ubuntu/ibus-qt importance medium affects ubuntu/ifpgui importance medium affects ubuntu/ifrit importance medium affects ubuntu/ike importance medium affects ubuntu/imagevis3d importance medium affects ubuntu/jovie importance medium affects ubuntu/jreen importance medium affects ubuntu/kaccessible importance medium affects ubuntu/kactivities importance medium affects ubuntu/kalternatives importance medium affects ubuntu/kamerka importance medium affects ubuntu/karlyriceditor importance medium affects ubuntu/kate4 importance medium affects ubuntu/kchmviewer importance medium affects ubuntu/kcm-qt-graphicssystem importance medium affects ubuntu/kcollectd importance medium affects ubuntu/kdbg importance medium affects ubuntu/kde4libs importance medium affects ubuntu/kde4pimlibs importance medium affects ubuntu/kde-baseapps importance medium affects ubuntu/kdepim4 importance medium affects ubuntu/kde-runtime importan
[Touch-packages] [Bug 1757320] Re: Remove Qt 4 from the archive
** Description changed: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or the whole source package removal) before the 19.04 release. If it is possible to do this by the 18.10 release, please do so. No new packages entering the Ubuntu archive should depend on qt4-x11 or any package which directly or indirectly depends on it. [1] https://wiki.debian.org/Qt4Removal - affects ubuntu/acoustid-fingerprinter - importance medium - affects ubuntu/adwaita-qt - importance medium - affects ubuntu/akonadi4 - importance medium - affects ubuntu/alsoft-conf - importance medium - affects ubuntu/alt-key - importance medium - affects ubuntu/amarok - importance medium - affects ubuntu/amora-server - importance medium - affects ubuntu/ams - importance medium - affects ubuntu/analitza4 - importance medium - affects ubuntu/appmenu-qt - importance medium - affects ubuntu/aseba - importance medium - affects ubuntu/attal - importance medium - affects ubuntu/attica - importance medium - affects ubuntu/auralquiz - importance medium - affects ubuntu/automoc - importance medium - affects ubuntu/autopilot-qt - importance medium - affects ubuntu/avogadro - importance medium - affects ubuntu/bacula - importance medium - affects ubuntu/ball - importance medium - affects ubuntu/baloo - importance medium - affects ubuntu/basket - importance medium - affects ubuntu/boats - importance medium - affects ubuntu/bodega-client - importance medium - affects ubuntu/bppphyview - importance medium - affects ubuntu/breeze - importance medium - affects ubuntu/cagibi - importance medium - affects ubuntu/cdcat - importance medium - affects ubuntu/chinese-calendar - importance medium - affects ubuntu/choreonoid - importance medium - affects ubuntu/clementine - importance medium - affects ubuntu/cmtk - importance medium - affects ubuntu/codelite - importance medium - affects ubuntu/codequery - importance medium - affects ubuntu/collatinus - importance medium - affects ubuntu/colord-kde - importance medium - affects ubuntu/connectome-workbench - importance medium - affects ubuntu/cortina - importance medium - affects ubuntu/cppreference-doc - importance medium - affects ubuntu/daemonfs - importance medium - affects ubuntu/dc-qt - importance medium - affects ubuntu/dee-qt - importance medium - affects ubuntu/dgedit - importance medium - affects ubuntu/dhcpcd-ui - importance medium - affects ubuntu/doomsday - importance medium - affects ubuntu/dssi - importance medium - affects ubuntu/enki-aseba - importance medium - affects ubuntu/eqonomize - importance medium - affects ubuntu/esperanza - importance medium - affects ubuntu/fbreader - importance medium - affects ubuntu/fcitx - importance medium - affects ubuntu/fcitx-kkc - importance medium - affects ubuntu/felix-latin - importance medium - affects ubuntu/flightcrew - importance medium - affects ubuntu/fmit - importance medium - affects ubuntu/fraqtive - importance medium - affects ubuntu/freecad - importance medium - affects ubuntu/freemat - importance medium - affects ubuntu/freemedforms-project - importance medium - affects ubuntu/freeplayer - importance medium - affects ubuntu/gammaray - importance medium - affects ubuntu/gebabbel - importance medium - affects ubuntu/genpo - importance medium - affects ubuntu/gle-graphics - importance medium - affects ubuntu/gmic - importance medium - affects ubuntu/gnash - importance medium - affects ubuntu/gnudoq - importance medium - affects ubuntu/grantlee - importance medium - affects ubuntu/gr-fosphor - importance medium - affects ubuntu/gr-radar - importance medium - affects ubuntu/gwenrename - importance medium - affects ubuntu/hamfax - importance medium - affects ubuntu/hedgewars - importance medium - affects ubuntu/heimdall-flash - importance medium - affects ubuntu/holdingnuts - importance medium - affects ubuntu/hydrogen - importance medium - affects ubuntu/ibus-qt - importance medium - affects ubuntu/ifpgui - importance medium - affects ubuntu/ifrit - importance medium - affects ubuntu/ike - importance medium - affects ubuntu/imagevis3d - importance medium - affects ubuntu/jovie - importance medium - affects ubuntu/jreen - importance medium - affects ubuntu/kaccessible - importance medium - affects ubuntu/kactivities - importance medium - affects ubuntu/kalternatives - importance medium - affects ubuntu/kamerka - importance medium - affects ubuntu/karlyriceditor - importance medium - affects ubuntu/kate4 - importance medium - affects ubuntu/kchmvi
[Touch-packages] [Bug 1757320] Re: Remove Qt 4 from the archive
** Description changed: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or the whole source package removal) before the 19.04 release. If it is possible to do this by the 18.10 release, please do so. No new packages entering the Ubuntu archive should depend on qt4-x11 or any package which directly or indirectly depends on it. [1] https://wiki.debian.org/Qt4Removal - - Â affects ubuntu/acoustid-fingerprinter - Â importance medium - Â affects ubuntu/adwaita-qt - Â importance medium - Â affects ubuntu/akonadi4 - Â importance medium - Â affects ubuntu/alsoft-conf - Â importance medium - Â affects ubuntu/alt-key - Â importance medium - Â affects ubuntu/amarok - Â importance medium - Â affects ubuntu/amora-server - Â importance medium - Â affects ubuntu/ams - Â importance medium - Â affects ubuntu/analitza4 - Â importance medium - Â affects ubuntu/appmenu-qt - Â importance medium - Â affects ubuntu/aseba - Â importance medium - Â affects ubuntu/attal - Â importance medium - Â affects ubuntu/attica - Â importance medium - Â affects ubuntu/auralquiz - Â importance medium - Â affects ubuntu/automoc - Â importance medium - Â affects ubuntu/autopilot-qt - Â importance medium - Â affects ubuntu/avogadro - Â importance medium - Â affects ubuntu/bacula - Â importance medium - Â affects ubuntu/ball - Â importance medium - Â affects ubuntu/baloo - Â importance medium - Â affects ubuntu/basket - Â importance medium - Â affects ubuntu/boats - Â importance medium - Â affects ubuntu/bodega-client - Â importance medium - Â affects ubuntu/bppphyview - Â importance medium - Â affects ubuntu/breeze - Â importance medium - Â affects ubuntu/cagibi - Â importance medium - Â affects ubuntu/cdcat - Â importance medium - Â affects ubuntu/chinese-calendar - Â importance medium - Â affects ubuntu/choreonoid - Â importance medium - Â affects ubuntu/clementine - Â importance medium - Â affects ubuntu/cmtk - Â importance medium - Â affects ubuntu/codelite - Â importance medium - Â affects ubuntu/codequery - Â importance medium - Â affects ubuntu/collatinus - Â importance medium - Â affects ubuntu/colord-kde - Â importance medium - Â affects ubuntu/connectome-workbench - Â importance medium - Â affects ubuntu/cortina - Â importance medium - Â affects ubuntu/cppreference-doc - Â importance medium - Â affects ubuntu/daemonfs - Â importance medium - Â affects ubuntu/dc-qt - Â importance medium - Â affects ubuntu/dee-qt - Â importance medium - Â affects ubuntu/dgedit - Â importance medium - Â affects ubuntu/dhcpcd-ui - Â importance medium - Â affects ubuntu/doomsday - Â importance medium - Â affects ubuntu/dssi - Â importance medium - Â affects ubuntu/enki-aseba - Â importance medium - Â affects ubuntu/eqonomize - Â importance medium - Â affects ubuntu/esperanza - Â importance medium - Â affects ubuntu/fbreader - Â importance medium - Â affects ubuntu/fcitx - Â importance medium - Â affects ubuntu/fcitx-kkc - Â importance medium - Â affects ubuntu/felix-latin - Â importance medium - Â affects ubuntu/flightcrew - Â importance medium - Â affects ubuntu/fmit - Â importance medium - Â affects ubuntu/fraqtive - Â importance medium - Â affects ubuntu/freecad - Â importance medium - Â affects ubuntu/freemat - Â importance medium - Â affects ubuntu/freemedforms-project - Â importance medium - Â affects ubuntu/freeplayer - Â importance medium - Â affects ubuntu/gammaray - Â importance medium - Â affects ubuntu/gebabbel - Â importance medium - Â affects ubuntu/genpo - Â importance medium - Â affects ubuntu/gle-graphics - Â importance medium - Â affects ubuntu/gmic - Â importance medium - Â affects ubuntu/gnash - Â importance medium - Â affects ubuntu/gnudoq - Â importance medium - Â affects ubuntu/grantlee - Â importance medium - Â affects ubuntu/gr-fosphor - Â importance medium - Â affects ubuntu/gr-radar - Â importance medium - Â affects ubuntu/gwenrename - Â importance medium - Â affects ubuntu/hamfax - Â importance medium - Â affects ubuntu/hedgewars - Â importance medium - Â affects ubuntu/heimdall-flash - Â importance medium - Â affects ubuntu/holdingnuts - Â importance medium - Â affects ubuntu/hydrogen - Â importance medium - Â affects ubuntu/ibus-qt - Â importance medium - Â affects ubuntu/ifpgui - Â importance medium - Â affects ubuntu/ifrit - Â importance medium - Â affects ubuntu/ike - Â importance medium - Â affects ubuntu/imagevis3d - Â importance medium - Â affects ubuntu/jovie - Â importance medium - Â affects ubuntu/jreen - Â importance medium - Â affects ubuntu/kaccessible - Â importance medium - Â affects ubuntu/kactivities - Â importance medium - Â affects ubuntu/kalternatives - Â importance medium - Â affects ubuntu/kamerka - Â importance medium - Â affects ubuntu/karlyriceditor - Â importance medium - Â affects ubuntu/kate4 - Â importance medium - Â affects ubuntu/kchmvi
[Touch-packages] [Bug 1757320] Re: Remove Qt 4 from the archive
** Changed in: kdesudo (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot-qt in Ubuntu. https://bugs.launchpad.net/bugs/1757320 Title: Remove Qt 4 from the archive Status in acoustid-fingerprinter package in Ubuntu: New Status in adwaita-qt package in Ubuntu: New Status in akonadi4 package in Ubuntu: New Status in alsoft-conf package in Ubuntu: New Status in alt-key package in Ubuntu: New Status in amarok package in Ubuntu: New Status in amora-server package in Ubuntu: New Status in ams package in Ubuntu: New Status in analitza4 package in Ubuntu: New Status in appmenu-qt package in Ubuntu: New Status in aseba package in Ubuntu: New Status in attal package in Ubuntu: New Status in attica package in Ubuntu: New Status in auralquiz package in Ubuntu: New Status in automoc package in Ubuntu: New Status in autopilot-qt package in Ubuntu: New Status in avogadro package in Ubuntu: New Status in bacula package in Ubuntu: New Status in ball package in Ubuntu: New Status in baloo package in Ubuntu: New Status in basket package in Ubuntu: New Status in boats package in Ubuntu: New Status in bodega-client package in Ubuntu: New Status in bppphyview package in Ubuntu: New Status in breeze package in Ubuntu: New Status in cagibi package in Ubuntu: New Status in cdcat package in Ubuntu: New Status in chinese-calendar package in Ubuntu: New Status in choreonoid package in Ubuntu: New Status in clementine package in Ubuntu: New Status in cmtk package in Ubuntu: New Status in codelite package in Ubuntu: New Status in codequery package in Ubuntu: New Status in collatinus package in Ubuntu: New Status in colord-kde package in Ubuntu: New Status in connectome-workbench package in Ubuntu: New Status in cortina package in Ubuntu: New Status in cppreference-doc package in Ubuntu: New Status in daemonfs package in Ubuntu: New Status in dc-qt package in Ubuntu: New Status in dee-qt package in Ubuntu: New Status in dgedit package in Ubuntu: New Status in dhcpcd-ui package in Ubuntu: New Status in doomsday package in Ubuntu: New Status in dssi package in Ubuntu: New Status in enki-aseba package in Ubuntu: New Status in eqonomize package in Ubuntu: New Status in esperanza package in Ubuntu: New Status in fbreader package in Ubuntu: New Status in fcitx package in Ubuntu: New Status in fcitx-kkc package in Ubuntu: New Status in felix-latin package in Ubuntu: New Status in flightcrew package in Ubuntu: New Status in fmit package in Ubuntu: New Status in fraqtive package in Ubuntu: New Status in freecad package in Ubuntu: New Status in freemat package in Ubuntu: New Status in freemedforms-project package in Ubuntu: New Status in freeplayer package in Ubuntu: New Status in gammaray package in Ubuntu: New Status in gebabbel package in Ubuntu: New Status in genpo package in Ubuntu: New Status in gle-graphics package in Ubuntu: New Status in gmic package in Ubuntu: New Status in gnash package in Ubuntu: New Status in gnudoq package in Ubuntu: New Status in gr-fosphor package in Ubuntu: New Status in gr-radar package in Ubuntu: New Status in grantlee package in Ubuntu: New Status in gwenrename package in Ubuntu: New Status in hamfax package in Ubuntu: New Status in hedgewars package in Ubuntu: New Status in heimdall-flash package in Ubuntu: New Status in holdingnuts package in Ubuntu: New Status in hydrogen package in Ubuntu: New Status in ibus-qt package in Ubuntu: New Status in ifpgui package in Ubuntu: New Status in ifrit package in Ubuntu: New Status in ike package in Ubuntu: New Status in imagevis3d package in Ubuntu: New Status in jovie package in Ubuntu: New Status in jreen package in Ubuntu: New Status in kaccessible package in Ubuntu: New Status in kactivities package in Ubuntu: New Status in kalternatives package in Ubuntu: New Status in kamerka package in Ubuntu: New Status in karlyriceditor package in Ubuntu: New Status in kate4 package in Ubuntu: New Status in kchmviewer package in Ubuntu: New Status in kcm-qt-graphicssystem package in Ubuntu: New Status in kcollectd package in Ubuntu: New Status in kdbg package in Ubuntu: New Status in kde-baseapps package in Ubuntu: New Status in kde-runtime package in Ubuntu: New Status in kde-thumbnailer-openoffice package in Ubuntu: New Status in kde4libs package in Ubuntu: New Status in kde4pimlibs package in Ubuntu: New Status in kdepim4 package in Ubuntu: New Status in kdesudo package in Ubuntu: Confirmed Status in kdiff3 package in Ubuntu: New Status in kdoctools package in Ubuntu: New Status in keepassx package in Ubuntu: New Status in kepas package in Ubuntu: New Status in keurocalc package in Ubuntu: New Status in kffmpegthumbnailer package in Ubuntu: New
[Touch-packages] [Bug 1757320] kdesudo can go soon
kdesudo can be removed from the archive as soon as my merged ubuntu-release-upgrader change has been uploaded and has migrated. $ reverse-depends src:kdesudo Reverse-Depends === * ubuntu-release-upgrader-qt(for kdesudo) $ reverse-depends -b src:kdesudo No reverse dependencies found -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot-qt in Ubuntu. https://bugs.launchpad.net/bugs/1757320 Title: Remove Qt 4 from the archive Status in acoustid-fingerprinter package in Ubuntu: New Status in adwaita-qt package in Ubuntu: New Status in akonadi4 package in Ubuntu: New Status in alsoft-conf package in Ubuntu: New Status in alt-key package in Ubuntu: New Status in amarok package in Ubuntu: New Status in amora-server package in Ubuntu: New Status in ams package in Ubuntu: New Status in analitza4 package in Ubuntu: New Status in appmenu-qt package in Ubuntu: New Status in aseba package in Ubuntu: New Status in attal package in Ubuntu: New Status in attica package in Ubuntu: New Status in auralquiz package in Ubuntu: New Status in automoc package in Ubuntu: New Status in autopilot-qt package in Ubuntu: New Status in avogadro package in Ubuntu: New Status in bacula package in Ubuntu: New Status in ball package in Ubuntu: New Status in baloo package in Ubuntu: New Status in basket package in Ubuntu: New Status in boats package in Ubuntu: New Status in bodega-client package in Ubuntu: New Status in bppphyview package in Ubuntu: New Status in breeze package in Ubuntu: New Status in cagibi package in Ubuntu: New Status in cdcat package in Ubuntu: New Status in chinese-calendar package in Ubuntu: New Status in choreonoid package in Ubuntu: New Status in clementine package in Ubuntu: New Status in cmtk package in Ubuntu: New Status in codelite package in Ubuntu: New Status in codequery package in Ubuntu: New Status in collatinus package in Ubuntu: New Status in colord-kde package in Ubuntu: New Status in connectome-workbench package in Ubuntu: New Status in cortina package in Ubuntu: New Status in cppreference-doc package in Ubuntu: New Status in daemonfs package in Ubuntu: New Status in dc-qt package in Ubuntu: New Status in dee-qt package in Ubuntu: New Status in dgedit package in Ubuntu: New Status in dhcpcd-ui package in Ubuntu: New Status in doomsday package in Ubuntu: New Status in dssi package in Ubuntu: New Status in enki-aseba package in Ubuntu: New Status in eqonomize package in Ubuntu: New Status in esperanza package in Ubuntu: New Status in fbreader package in Ubuntu: New Status in fcitx package in Ubuntu: New Status in fcitx-kkc package in Ubuntu: New Status in felix-latin package in Ubuntu: New Status in flightcrew package in Ubuntu: New Status in fmit package in Ubuntu: New Status in fraqtive package in Ubuntu: New Status in freecad package in Ubuntu: New Status in freemat package in Ubuntu: New Status in freemedforms-project package in Ubuntu: New Status in freeplayer package in Ubuntu: New Status in gammaray package in Ubuntu: New Status in gebabbel package in Ubuntu: New Status in genpo package in Ubuntu: New Status in gle-graphics package in Ubuntu: New Status in gmic package in Ubuntu: New Status in gnash package in Ubuntu: New Status in gnudoq package in Ubuntu: New Status in gr-fosphor package in Ubuntu: New Status in gr-radar package in Ubuntu: New Status in grantlee package in Ubuntu: New Status in gwenrename package in Ubuntu: New Status in hamfax package in Ubuntu: New Status in hedgewars package in Ubuntu: New Status in heimdall-flash package in Ubuntu: New Status in holdingnuts package in Ubuntu: New Status in hydrogen package in Ubuntu: New Status in ibus-qt package in Ubuntu: New Status in ifpgui package in Ubuntu: New Status in ifrit package in Ubuntu: New Status in ike package in Ubuntu: New Status in imagevis3d package in Ubuntu: New Status in jovie package in Ubuntu: New Status in jreen package in Ubuntu: New Status in kaccessible package in Ubuntu: New Status in kactivities package in Ubuntu: New Status in kalternatives package in Ubuntu: New Status in kamerka package in Ubuntu: New Status in karlyriceditor package in Ubuntu: New Status in kate4 package in Ubuntu: New Status in kchmviewer package in Ubuntu: New Status in kcm-qt-graphicssystem package in Ubuntu: New Status in kcollectd package in Ubuntu: New Status in kdbg package in Ubuntu: New Status in kde-baseapps package in Ubuntu: New Status in kde-runtime package in Ubuntu: New Status in kde-thumbnailer-openoffice package in Ubuntu: New Status in kde4libs package in Ubuntu: New Status in kde4pimlibs package in Ubuntu: New Status in kdepim4 package in Ubuntu: New Status in kdesudo package in Ubuntu: Confirmed Status in kdiff3 package in Ubuntu
[Touch-packages] [Bug 1757747] [NEW] Please port your package away from Qt 4
Public bug reported: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: qt4-removal -- 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/1757747 Title: Please port your package away from Qt 4 Status in lightdm package in Ubuntu: New Bug description: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1757747/+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 1757730] [NEW] Please port your package away from Qt 4
Public bug reported: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal ** Affects: libdbusmenu-qt (Ubuntu) Importance: Undecided Status: New ** Tags: qt4-removal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdbusmenu-qt in Ubuntu. https://bugs.launchpad.net/bugs/1757730 Title: Please port your package away from Qt 4 Status in libdbusmenu-qt package in Ubuntu: New Bug description: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1757730/+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 1757915] [NEW] Please port your package away from Qt 4
Public bug reported: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal ** Affects: zbar (Ubuntu) Importance: Undecided Status: New ** Tags: qt4-removal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zbar in Ubuntu. https://bugs.launchpad.net/bugs/1757915 Title: Please port your package away from Qt 4 Status in zbar package in Ubuntu: New Bug description: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zbar/+bug/1757915/+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 1757884] [NEW] Please port your package away from Qt 4
Public bug reported: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal ** Affects: syncevolution (Ubuntu) Importance: Undecided Status: New ** Tags: qt4-removal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to syncevolution in Ubuntu. https://bugs.launchpad.net/bugs/1757884 Title: Please port your package away from Qt 4 Status in syncevolution package in Ubuntu: New Bug description: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/syncevolution/+bug/1757884/+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 1757320] Re: Remove Qt 4 from the archive
Instead of filing one megabug, I filed separate bugs: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=qt4-removal Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1757320 Title: Remove Qt 4 from the archive Status in qt4-x11 package in Ubuntu: New Bug description: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or the whole source package removal) before the 19.04 release. If it is possible to do this by the 18.10 release, please do so. No new packages entering the Ubuntu archive should depend on qt4-x11 or any package which directly or indirectly depends on it. [1] https://wiki.debian.org/Qt4Removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1757320/+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 1757625] [NEW] Please port your package away from Qt 4
Public bug reported: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal ** Affects: dee-qt (Ubuntu) Importance: Undecided Status: New ** Tags: qt4-removal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dee-qt in Ubuntu. https://bugs.launchpad.net/bugs/1757625 Title: Please port your package away from Qt 4 Status in dee-qt package in Ubuntu: New Bug description: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dee-qt/+bug/1757625/+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 1757600] [NEW] Please port your package away from Qt 4
Public bug reported: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal ** Affects: autopilot-qt (Ubuntu) Importance: Undecided Status: New ** Tags: qt4-removal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot-qt in Ubuntu. https://bugs.launchpad.net/bugs/1757600 Title: Please port your package away from Qt 4 Status in autopilot-qt package in Ubuntu: New Bug description: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopilot-qt/+bug/1757600/+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 1757320] Re: Remove Qt 4 from the archive
** Tags added: qt4-removal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1757320 Title: Remove Qt 4 from the archive Status in qt4-x11 package in Ubuntu: New Bug description: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or the whole source package removal) before the 19.04 release. If it is possible to do this by the 18.10 release, please do so. No new packages entering the Ubuntu archive should depend on qt4-x11 or any package which directly or indirectly depends on it. [1] https://wiki.debian.org/Qt4Removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1757320/+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 1757730] Re: Please port your package away from Qt 4
** Bug watch added: Debian Bug tracker #875021 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875021 ** Also affects: libdbusmenu-qt (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875021 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdbusmenu-qt in Ubuntu. https://bugs.launchpad.net/bugs/1757730 Title: Please port your package away from Qt 4 Status in libdbusmenu-qt package in Ubuntu: New Status in libdbusmenu-qt package in Debian: Unknown Bug description: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1757730/+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 1757884] Re: Please port your package away from Qt 4
** Bug watch added: Debian Bug tracker #875215 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875215 ** Also affects: syncevolution (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875215 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to syncevolution in Ubuntu. https://bugs.launchpad.net/bugs/1757884 Title: Please port your package away from Qt 4 Status in syncevolution package in Ubuntu: New Status in syncevolution package in Debian: Unknown Bug description: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/syncevolution/+bug/1757884/+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 1757915] Re: Please port your package away from Qt 4
** Bug watch added: Debian Bug tracker #875246 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875246 ** Also affects: zbar (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875246 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zbar in Ubuntu. https://bugs.launchpad.net/bugs/1757915 Title: Please port your package away from Qt 4 Status in zbar package in Ubuntu: New Status in zbar package in Debian: Unknown Bug description: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zbar/+bug/1757915/+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 1758551] Re: bionic install uses 3.26 gnome snaps instead of 3.28 packages
** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1758551 Title: bionic install uses 3.26 gnome snaps instead of 3.28 packages Status in ubuntu-meta package in Ubuntu: New Bug description: The current bionic installer is incorrectly installing snap versions of gnome-calculator, gnome-characters and gnome-system-monitor from the Gnome 3.26 release rather than the newer 3.28 normal deb packages present in the bionic repo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1758551/+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 243105] Re: When Wubi is installed from CD, ubiquity crashes at the end of the installation
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once: apport-collect 243105 and any other logs that are relevant for this particular issue. ** Changed in: apt (Ubuntu) Status: New => Incomplete ** Changed in: ubiquity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/243105 Title: When Wubi is installed from CD, ubiquity crashes at the end of the installation Status in Wubi: Confirmed Status in apt package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: Incomplete Bug description: Because of bug #207137 Wubi now copies the CD content as opposed to extract an ISO. This was implemented via bug #230716 which allows casper to boot off a directory. That directory is bindmounted to /cdrom in the initrd. But that makes ubiquity/install.py > install_extras > do_install > cache.commit fail, since apt/python-apt does not work correctly when /cdrom is bind-mounted. That in turn can be tracked down to fetcher.Run() in apt/cache.py cache.py > Cache.commit > Cache._fetchArchives > self._runFetcher(fetcher) > fetcher.Run() Where fetcher = apt_pkg.GetAcquire(fetchProgress) -> Acquire instance When installing Wubi from an ISO (no bindmount) or when setting up /cdrom via a symlink in casper, the installation proceeds correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/wubi/+bug/243105/+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 1435465] Re: Alt+F4 crashes app where WebView embedded in a Window
Seems like this is fixed now. ** Changed in: qtbase-opensource-src (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1435465 Title: Alt+F4 crashes app where WebView embedded in a Window Status in qtbase-opensource-src package in Ubuntu: Fix Released Bug description: was just watching something on Youtube Web App created by unity itself. when i pressed alt-f4 Ubuntu said it had an error and if i want to submit it. that is all folks. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: webapp-container 0.23+15.04.20150320.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 23 19:56:16 2015 Disassembly: => 0x0: Cannot access memory at address 0x0 ExecutablePath: /usr/bin/webapp-container InstallationDate: Installed on 2015-03-22 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150306) ProcCmdline: webapp-container --app-id=YouTubeyoutubecom --webapp=WW91VHViZQ== --enable-back-forward SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: webbrowser-app StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so Title: webapp-container crashed with SIGSEGV in QMetaObject::activate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1435465/+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 1649262] Re: webbrowser app Segmentation fault (core dumped) on 17.04 Unity7
Is this still a bug? ** Changed in: qtdeclarative-opensource-src (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1649262 Title: webbrowser app Segmentation fault (core dumped) on 17.04 Unity7 Status in Canonical System Image: Confirmed Status in qtdeclarative-opensource-src package in Ubuntu: Incomplete Bug description: 17.04 unity7 ~$ webbrowser-app libGL error: MESA-LOADER: failed to retrieve device information libGL error: Version 4 or later of flush extension not found libGL error: failed to load driver: i915 libGL error: MESA-LOADER: failed to retrieve device information (webbrowser-app:4695): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. (webbrowser-app:4695): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. (webbrowser-app:4695): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. UCUriHandler: Empty "APP_ID" environment variable, ignoring. unity::action::ActionManager::ActionManager(QObject*): Could not determine application identifier. HUD will not work properly. Provide your application identifier in $APP_ID environment variable. libGL error: MESA-LOADER: failed to retrieve device information libGL error: Version 4 or later of flush extension not found libGL error: failed to load driver: i915 libGL error: MESA-LOADER: failed to retrieve device information could not open containers config file "/home/pixel/.local/share/libertine/ContainersConfig.json" APP_ID isn't set, the handler can not be registered Input device added: "Power Button" "/dev/input/event1" QFlags(0x1) Input device added: "Power Button" "/dev/input/event0" QFlags(0x1) Input device added: "HDA Intel PCH Line Out" "/dev/input/event7" QFlags(0x20) Input device added: "HDA Intel PCH Rear Mic" "/dev/input/event5" QFlags(0x20) Input device added: "HDA Intel PCH Line" "/dev/input/event6" QFlags(0x20) Input device added: "YSPRINGTECH USB OPTICAL MOUSE" "/dev/input/event2" QFlags(0x2) Input device added: "USB USB Keykoard" "/dev/input/event3" QFlags(0x1|0x10) Input device added: "USB USB Keykoard" "/dev/input/event4" QFlags(0x1) (webbrowser-app:4695): IBUS-WARNING **: Unable to connect to ibus: Could not connect: Permission denied QOpenGLShader: could not create shader QOpenGLShader: could not create shader QOpenGLShader: could not create shader QOpenGLShader: could not create shader QOpenGLShader: could not create shader QOpenGLShader: could not create shader APP_ID isn't set, the handler ignored qml: Loaded 13 UA override(s) from file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web/ua-overrides-desktop.js ^CSegmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1649262/+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 1760266] Re: Will not install debs
*** This bug is a duplicate of bug 1756238 *** https://bugs.launchpad.net/bugs/1756238 ** This bug has been marked a duplicate of bug 1756238 gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1760266 Title: Will not install debs Status in gdebi package in Ubuntu: New Bug description: When I open a deb file with gdebi, all loads fine. When I click on install, it will ask for authentication as normal, but it will not actually install anything after. It flashes something I Cannot see/read, then I get the reloading bar, and when it is done reloading, it is the same initial window offering to install. It does not say installed or have any of the associated options, like reinstall. I can verify the package is not actually getting installed and it is not just a GUI glitch. I am able to install the same deb files using "Software Install" as well as dpkg without any issues. Package Manager also works fine, and I use it for most all things. I also use apt and apt-get, which both also work fine. I am using Ubuntu 18.04 MATE 1.20, all updates current always within 24 hours. I run updates about twice per day. Guideline requirements: $ lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 $ apt-cache policy gdebi gdebi: Installed: 0.9.5.7+nmu2 Candidate: 0.9.5.7+nmu2 Version table: *** 0.9.5.7+nmu2 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1760266/+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 1760435] Re: Use Ubuntu language packs for various indicators
Hello. I'll prepare all of the uploads in Bileto: https://bileto.ubuntu.com/#/ticket/3221 This is mapped to this PPA: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/3221/+packages I'll upload this set of packages there, but then I'd like some verification that this is the whole stack that needs these changes. I also want to know that these changes work... ** Changed in: indicator-datetime (Ubuntu) Assignee: (unassigned) => Simon Quigley (tsimonq2) ** Changed in: indicator-messages (Ubuntu) Assignee: (unassigned) => Simon Quigley (tsimonq2) ** Changed in: indicator-power (Ubuntu) Assignee: (unassigned) => Simon Quigley (tsimonq2) ** Changed in: indicator-session (Ubuntu) Assignee: (unassigned) => Simon Quigley (tsimonq2) ** Changed in: indicator-sound (Ubuntu) Assignee: (unassigned) => Simon Quigley (tsimonq2) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1760435 Title: Use Ubuntu language packs for various indicators Status in indicator-datetime package in Ubuntu: Confirmed Status in indicator-messages package in Ubuntu: Confirmed Status in indicator-power package in Ubuntu: Confirmed Status in indicator-session package in Ubuntu: Confirmed Status in indicator-sound package in Ubuntu: Confirmed Bug description: The Unity family of packages was previously part of standard Ubuntu. Thus all the translation templates were made available to the translators via Launchpad, and the translations were included in the language packs. Since those packages are no longer part of standard Ubuntu, they have been moved from main to universe. And translations are dropped. At the moment, it is feasible for us to keep using langpacks. That means adding "X-Ubuntu-Use-Langpack: yes" to their debian/control and doing an upload. See: https://community.ubuntu.com/t/translation-of-unity-packages/4919 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1760435/+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 1760435] Re: Use Ubuntu language packs for various indicators
On further investigation, out of the packages marked as affected, only indicator-datetime needed the change. Uploaded to the PPA. ** Changed in: indicator-messages (Ubuntu) Assignee: Simon Quigley (tsimonq2) => (unassigned) ** Changed in: indicator-power (Ubuntu) Assignee: Simon Quigley (tsimonq2) => (unassigned) ** Changed in: indicator-session (Ubuntu) Assignee: Simon Quigley (tsimonq2) => (unassigned) ** Changed in: indicator-sound (Ubuntu) Assignee: Simon Quigley (tsimonq2) => (unassigned) ** Changed in: indicator-messages (Ubuntu) Status: Confirmed => Invalid ** Changed in: indicator-session (Ubuntu) Status: Confirmed => Invalid ** Changed in: indicator-power (Ubuntu) Status: Confirmed => Invalid ** Changed in: indicator-sound (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1760435 Title: Use Ubuntu language packs for various indicators Status in indicator-datetime package in Ubuntu: Confirmed Status in indicator-messages package in Ubuntu: Invalid Status in indicator-power package in Ubuntu: Invalid Status in indicator-session package in Ubuntu: Invalid Status in indicator-sound package in Ubuntu: Invalid Bug description: The Unity family of packages was previously part of standard Ubuntu. Thus all the translation templates were made available to the translators via Launchpad, and the translations were included in the language packs. Since those packages are no longer part of standard Ubuntu, they have been moved from main to universe. And translations are dropped. At the moment, it is feasible for us to keep using langpacks. That means adding "X-Ubuntu-Use-Langpack: yes" to their debian/control and doing an upload. See: https://community.ubuntu.com/t/translation-of-unity-packages/4919 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1760435/+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 1760435] Re: Use Ubuntu language packs for various indicators
> Ready for the archive IMO. :) Thanks! Cool! > Are you saying that that line is there already for all the other indicator-* packages? Yep. > Can you please also check out the unity-* packages, for instance those I mentioned in the community hub. I'd like a full list of packages needed here before I start making assumptions. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1760435 Title: Use Ubuntu language packs for various indicators Status in indicator-datetime package in Ubuntu: Confirmed Status in indicator-messages package in Ubuntu: Invalid Status in indicator-power package in Ubuntu: Invalid Status in indicator-session package in Ubuntu: Invalid Status in indicator-sound package in Ubuntu: Invalid Bug description: The Unity family of packages was previously part of standard Ubuntu. Thus all the translation templates were made available to the translators via Launchpad, and the translations were included in the language packs. Since those packages are no longer part of standard Ubuntu, they have been moved from main to universe. And translations are dropped. At the moment, it is feasible for us to keep using langpacks. That means adding "X-Ubuntu-Use-Langpack: yes" to their debian/control and doing an upload. See: https://community.ubuntu.com/t/translation-of-unity-packages/4919 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1760435/+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 1760411] Re: I don know
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1760411 Title: I don know Status in xorg package in Ubuntu: Incomplete Bug description: i don know ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Apr 1 16:29:14 2018 DistUpgraded: 2018-03-31 14:06:35,805 DEBUG /openCache(), new cache size 86473 DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.34, 4.13.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Broadwell-U Integrated Graphics [103c:80c1] InstallationDate: Installed on 2018-03-26 (5 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: HP HP Notebook ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2018-03-31 (1 days ago) dmi.bios.date: 10/27/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C1 dmi.board.vendor: HP dmi.board.version: 96.51 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd10/27/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80C1:rvr96.51:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Mar 31 13:56:55 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1760411/+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
