I'll call this good. :)
** Changed in: etcd (Ubuntu)
Status: New => Fix Released
** Bug watch added: github.com/coreos/etcd/issues #8715
https://github.com/coreos/etcd/issues/8715
** Bug watch added: github.com/ugorji/go/issues #224
https://github.com/ugorji/go/issues/224
--
You
This bug was fixed in the package etcd - 3.2.17+dfsg-1
Sponsored for Anthony Fok (foka)
---
etcd (3.2.17+dfsg-1) unstable; urgency=medium
* New upstream release.
* Fix FTBFS:
- New upstream release contains regenerated gRPC *.pb.go and *.pb.gw.po
files (since etcd
@Doug re comment #10, I see exactly the same divide by zero error in the
syslog and gdm fails to boot when I prime-select nvidia. I'm using a
GP107M [GeForce GTX 1050 Mobile] card.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package colord-kde - 0.5.0-2
---
colord-kde (0.5.0-2) experimental; urgency=medium
* Initial Debian upload.
* Add myself as human uploader
* Bump debhelper compat to 9
* Bump Standards-Version to 3.9.8, no changes needed.
* Add homepage and vcs
This bug was fixed in the package golang-github-ugorji-go-codec -
1.1+git20180221.0076dd9-3
Sponsored for Anthony Fok (foka)
---
golang-github-ugorji-go-codec (1.1+git20180221.0076dd9-3) unstable;
urgency=medium
* Apply "cme fix dpkg" to debian/control and debian/copyright,
You're right. :)
Syncing from Debian...
** Changed in: colord-kde (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757619
Title:
Please port your package
Public bug reported:
The package won't install. That's all I know.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: mariadb-server-10.1 (not installed)
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
NonfreeKernelModules: openafs
This bug was fixed in the package colord-kde - 0.5.0-2
---
colord-kde (0.5.0-2) experimental; urgency=medium
* Initial Debian upload.
* Add myself as human uploader
* Bump debhelper compat to 9
* Bump Standards-Version to 3.9.8, no changes needed.
* Add homepage and vcs
*** This bug is a duplicate of bug 1752108 ***
https://bugs.launchpad.net/bugs/1752108
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1752108, so is being marked as such.
I backported the fix to Artful's kernel, so please follow instruction in
#38 and update the tag, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661876
Title:
[Asus UX360UA] battery status
Public bug reported:
downloaded the iso from peach osi's download page and wrote the iso to a
dvd. when running from a dvd for installation an error occurs in the
last 25%.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.6 [modified: usr/lib/ubiquity/ubiquity/misc.py
** Tags added: artful bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553466
Title:
org.gnome.SessionManager was not provided by any .service files
To manage notifications about this bug go
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: 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/1714667
Title:
please add
** Also affects: 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/1714667
Title:
please add old hungarian letters
To manage notifications about this
Does it also get fixed by latest upstream stable kernel?
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.12/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757218
Title:
QCA9377 isn't being
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1757937
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
The information attached to this report will claim that /etc/zfs/zed.d
/zed-functions.sh is a modified conffile because it has been "deleted".
What it actually is, is a dangling symlink.
lrwxrwxrwx 1 root root45 Feb 17 2017 /etc/zfs/zed.d/zed-
functions.sh ->
Obviously the user needs to reboot after a dist-upgrade for the new
system to be fully usable, but zed should degrade more gracefully than
by pegging the CPU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Confirmed this bug here - same situation, I did an upgrade from 17.10 to
18.04, and prior to reboot, zed is spinning using 100% of a core.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751796
Title:
Try kernel parameter "acpi_backlight=video" and "acpi_backlight=vendor"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751887
Title:
The brightness of the screen cannot be adjusted with either the
** Changed in: libinput
Status: Unknown => Confirmed
** Changed in: libinput
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757929
Title:
Lenovo Yoga 11S
** Changed in: linux (Ubuntu)
Status: Fix Committed => Triaged
** Changed in: hwe-next
Status: Fix Committed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731091
Title:
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1757561
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
The zram smoke test failed due to the absence of the zram module.
modprobe: FATAL: Module zram not found in directory
/lib/modules/4.13.0-1012-gcp
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
*** This bug is a duplicate of bug 545790 ***
https://bugs.launchpad.net/bugs/545790
** This bug has been marked a duplicate of bug 545790
package PACKAGE failed to install/upgrade: error writing to '': Success
--
You received this bug notification because you are a member of Ubuntu
[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for shim-signed (Ubuntu) because there has been no activity for
60 days.]
** Changed in: shim-signed (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: linux (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/1757561
Title:
Wifi disconnects randomly under ubuntu 17.10
To manage
[Expired for grub-installer (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: grub-installer (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Reviewing your log files attached to this bug report it
seems that a package failed to install due to a segmentation fault in
the application being used for the package installation process.
Unfortunately, this
Public bug reported:
111
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: fonts-stix 1.1.0-1
ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22
Uname: Linux 3.19.0-80-generic i686
ApportVersion: 2.14.1-0ubuntu3.27
AptdaemonVersion: 1.1.1-1ubuntu5.2
Architecture: i386
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757935
Title:
package fonts-stix 1.1.0-1 failed to install/upgrade: package fonts-
stix is already installed
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757934
Title:
package flash-kernel 3.0~rc.4ubuntu54+rpi2.4 failed to
install/upgrade: triggers looping,
The error in your log is:
update-notifier-common (3.168.8) wird eingerichtet ...
Traceback (most recent call last):
File "/usr/lib/update-notifier/package-data-downloader", line 24, in
import debian.deb822
ImportError: No module named 'debian'
dpkg: Fehler beim Bearbeiten des Paketes
Public bug reported:
automated crash report
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: flash-kernel 3.0~rc.4ubuntu54+rpi2.4
ProcVersionSignature: Ubuntu 3.18.0-20.21-rpi2 3.18.11
Uname: Linux 3.18.0-20-rpi2 armv7l
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: armhf
Date: Wed Mar
** Changed in: lightdm (Ubuntu)
Status: New => Triaged
** Changed in: lightdm (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757747
Title:
Please
Hello Matt, or anyone else affected,
Accepted grub2-signed into xenial-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/grub2-signed/1.66.18 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Awaiting information upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=104990
** Changed in: libinput (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757929
Title:
Lenovo Yoga 11S touchpad is numb and unresponsive with libinput 1.10.3
To manage notifications about this bug go
Kind of fix released...
https://bugs.freedesktop.org/show_bug.cgi?id=105675
** Bug watch added: freedesktop.org Bugzilla #105675
https://bugs.freedesktop.org/show_bug.cgi?id=105675
** Changed in: libinput (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug
Public bug reported:
Lenovo Yoga 11S touchpad is numb and unresponsive with libinput 1.10.3
Actually it starts out very jittery, but soon switches mode and becomes
numb and unresponsive (hysteresis margin feels too big maybe).
Workaround: xserver-xorg-input-synaptics works fine and has neither
** Changed in: scribus (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757865
Title:
Please port your package away from Qt 4
To manage notifications about
I'm also experiencing the same problem with Ubuntu 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621929
Title:
Scale for menu and title bars does not work if the slider is moved
with the
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
This was fixed upstream in 5.4.1, which is in artful.
** Changed in: therion (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667550
Title:
Edit
I further investigated this problem. My initial report was based on
annotations to a document sent by a bank. Some forums report that
document DRM properties affect the ability to create/edit annotation.
See:
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
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
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
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
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
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
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
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
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
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
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
** Changed in: mesa (Ubuntu Bionic)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753776
Title:
Graphics corruption just before login animation to Xorg sessions
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
Public bug reported:
zuma-p
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Critical
Assignee: Hui Wang (hui.wang)
Status: Incomplete
** Tags: originate-from-1749165 somerville
** Tags added:
*** This bug is a duplicate of bug 1693609 ***
https://bugs.launchpad.net/bugs/1693609
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 1693609, so it is being marked as such. Please
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1757584
and then change the status of the bug to 'Confirmed'.
If, due to the
I have released a Qt5 ported version of colord-kde more than a year ago
:D
https://download.kde.org/stable/colord-kde/0.5.0/src/
2018-03-21 23:01 GMT-03:00 Simon Quigley :
> Public bug reported:
>
> Currently Qt 4 has been dead upstream and we are starting to have
> problems
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
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
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
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
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
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
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
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
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
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
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
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
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 - 100 of 1057 matches
Mail list logo