[Bug 1757673] [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

[Bug 1757674] [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

[Bug 1757671] [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

[Bug 1757670] [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

[Bug 1757669] [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

[Bug 1757668] [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

[Bug 1757666] [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

[Bug 1757667] [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

[Bug 1757663] [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

[Bug 1757661] [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

[Bug 1757658] [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

[Bug 1757660] [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

[Bug 1757657] [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

[Bug 1757656] [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

[Bug 1757653] [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

[Bug 1757651] [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

[Bug 1757652] [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

[Bug 1757654] [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

[Bug 1757655] [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

[Bug 1757649] [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

[Bug 1757650] [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

[Bug 1757648] [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

[Bug 1757646] [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

[Bug 1757647] [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

[Bug 1757644] [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

[Bug 1757642] [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

[Bug 1757640] [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

[Bug 1757637] [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

[Bug 1757638] [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

[Bug 1757636] [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

[Bug 1757634] [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

[Bug 1757632] [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

[Bug 1757631] [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

[Bug 1757627] [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

[Bug 1757626] [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

[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

[Bug 1757620] [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

[Bug 1757621] [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

[Bug 1757584] Re: Let headset-mode initialization be called on Dell Precision 3930

** Description changed: - zuma-p + There is only one audio jack on this machine (codename: zuma-p), so + there is only one output device (headphone), then the driver will not generate + auto-mute control on this machine, without auto-mute, the headset-mode + initialization routine will not be

[Bug 1757582] Re: WebProcess crash rendering some email in Geary

** Also affects: geary (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757582 Title: WebProcess crash rendering some email in Geary To manage

[Bug 1757619] [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

[Bug 1757618] [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

[Bug 1757615] [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

[Bug 1757616] [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

[Bug 1757614] [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

[Bug 1757606] [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

[Bug 1757613] [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

[Bug 1757609] [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

[Bug 1757612] [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

[Bug 1757598] [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

[Bug 1757593] [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

[Bug 1757587] [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

[Bug 1757610] [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

[Bug 1757608] [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

[Bug 1757607] [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

[Bug 1757605] [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

[Bug 1757604] [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

[Bug 1757602] [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

[Bug 1757812] [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

[Bug 1757601] [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

[Bug 1756141] Re: Update to 0.6

This bug was fixed in the package libgepub - 0.6.0-1 --- libgepub (0.6.0-1) unstable; urgency=medium * New upstream release (LP: #1756141) * Update package names for new release * Have -dev package depend on libsoup2.4-dev and libwebkit2gtk4.0-dev -- Jeremy Bicha

[Bug 1757865] Re: Please port your package away from Qt 4

** Bug watch added: Debian Bug tracker #875180 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875180 ** Also affects: scribus (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875180 Importance: Unknown Status: Unknown -- You received this bug notification

[Bug 1757597] [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

[Bug 1757599] [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

[Bug 1757885] Re: Please port your package away from Qt 4

Synergy already builds on qt5. Relevant patches for Debian upstream are at https://github.com/epakai/synergy- debian/commit/e2b31c6e91b4b52f19884ffbf060cfe5b8904d92 There has also been a new release (1.9.0) from Symless in the past week. I probably need a few weeks to get to it, but I intend to

[Bug 1757594] [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

[Bug 1757592] [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

[Bug 1757589] [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

[Bug 1757746] Re: Please port your package away from Qt 4

** Changed in: libreoffice (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757746 Title: Please port your package away from Qt 4 To manage notifications

[Bug 1757586] [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

[Bug 1757585] [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

[Bug 1757584] Re: Let headset-mode initialization be called on Dell Precision 3930

The patch is in the mainline kernel now. commit ae104a21e52b1f9aab342cf6924405177b720069 Author: Kailang Yang Date: Mon Feb 5 16:07:20 2018 +0800 ALSA: hda/realtek - Add headset mode support for Dell laptop This platform was only one phone Jack. Add dummy

[Bug 1757467] Re: [kubuntu] No window borders around gnumeric program with wayland

It's a KDE/Kubuntu bug only. Not a bug in the Wayland protocol, and not a bug in Gnome Shell. ** Summary changed: - no windows arround gnumeric program with wayland + [kubuntu] No window borders around gnumeric program with wayland ** Package changed: wayland (Ubuntu) => kubuntu-meta (Ubuntu)

[Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unprocessed)

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: budgie-artwork (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750465

[Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unprocessed)

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-mate-artwork (Ubuntu Artful) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unprocessed)

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-mate-artwork (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750465

[Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unprocessed)

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-gnome-default-settings (Ubuntu Artful) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unprocessed)

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-gnome-default-settings (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unprocessed)

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: kubuntu-settings (Ubuntu Artful) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1754480] Re: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unprocessed

*** This bug is a duplicate of bug 1750465 *** https://bugs.launchpad.net/bugs/1750465 ** This bug is no longer a duplicate of bug 1754371 package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unprocessed ** This bug has been

[Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unprocessed)

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu Artful) Status: New => Confirmed -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-settings in Ubuntu.

[Bug 1757584] Re: Let headset-mode initialization be called on Dell Precision 3930

** Package changed: linux (Ubuntu) => linux-oem (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757584 Title: Let headset-mode initialization be called on Dell Precision 3930 To manage

[Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unprocessed)

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: budgie-artwork (Ubuntu Artful) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1754371] Re: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unprocessed

*** This bug is a duplicate of bug 1750465 *** https://bugs.launchpad.net/bugs/1750465 ** This bug has been marked a duplicate of bug 1750465 upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency

[Bug 1757467] Re: [kubuntu] No window borders around gnumeric program with wayland

** Package changed: kubuntu-meta (Ubuntu) => kwin (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757467 Title: [kubuntu] No window borders around gnumeric program with wayland To manage

[Bug 1755769] Re: linux-azure-edge: 4.15.0-1003.3 -proposed tracker

** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- +

[Bug 1757298] Re: GNOME Shell is consuming most of memory; Laptop RAM = 4 G.B; .

*** This bug is a duplicate of bug 1672297 *** https://bugs.launchpad.net/bugs/1672297 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1672297, so it is being marked as such. Please

[Bug 1754422] Re: [MIR] volume-key

With this commit, I now get this error: "Error creating passphrase-encrypted packet: GPGME: Bad passphrase" https://salsa.debian.org/utopia-team/volume-key/commit/42207b3d -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757320 Title: Remove Qt 4

[Bug 1693609] Re: The "Minimize", " Maximize" and "Close" buttons are too small to click

** Summary changed: - Please make window control buttons larger + The "Minimize", " Maximize" and "Close" buttons are too small to click ** Changed in: ubuntu-ux Status: New => Confirmed ** Changed in: ubuntu-themes (Ubuntu) Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned)

[Bug 1757682] Re: Please port your package away from Qt 4

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

[Bug 1754422] Re: [MIR] volume-key

I mean this part of the log seems like it's obviously not going to work. --- To begin, type keys on the keyboard until this progress meter is full. DO NOT USE THE AUTOREPEAT FUNCTION ON YOUR KEYBOARD! Continue typing until the

[Bug 1757823] [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

[Bug 1757815] [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

[Bug 1757822] [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

[Bug 1757811] [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

[Bug 1757819] [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

[Bug 1754422] Re: [MIR] volume-key

- Why did this not fail the build? Because then the build wouldn't work! I mentioned this in the MIR description under Quality Assurance. - Why did this fail? I don't know. Once we know how to get the tests to pass, I'll be happy to make test failures fail the build. (Currently, they're ignored

[Bug 1757809] [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

[Bug 1757824] [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

<    1   2   3   4   5   6   7   8   9   10   >