So this "fix" seems to cause Kernels released with zesty (and newer)
keep the monitor always ON. No blanking, and no power down either.
Before this fix, a clean install of Ubuntu server would signal the
monitor to sleep/standby after a short while. Now the default behavior
is to leave the monitor
If the location and shape of the problem never changes then one possible
explanation would be small areas of failing RAM on the graphics card.
It might also be a software bug of course.
** Summary changed:
- Screen displays dynamic corruptions
+ [nvidia] Screen displays dynamic corruptions
**
In the meantime, I brought arm64 back almost as soon as
https://salsa.debian.org/systemd-team/systemd/merge_requests/34 was
merged. It looks promising except that the "upstream" test is flaky
there as well. It'd be great to turn it off on Ubuntu CI.
--
You received this bug notification because
Public bug reported:
Regularly the screen displays corruptions that change depending on disk
i/o, keyboard/mouse and other system activity. The screen corruptions do
not appear on each session and can be removed by selecting an
alternative resolution and then changing back (or reverting without
Screen shots of the corruption do not work as the screen shot tool
appears to overwrite the corruption. Video capture does work.
** Attachment added: "Video capture of screen corruption"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1834554/+attachment/5273854/+files/screen-speckles.ogv
Thanks for working on this and preparing the debdiffs. Has the debian
package changed from interest to interest-noawait? Is there a bug in
debian regarding this issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gconf in
** Tags added: bionic
** Also affects: bzip2 (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bzip2 in Ubuntu.
https://bugs.launchpad.net/bugs/1834494
Title:
** Changed in: systemd (Debian)
Status: Confirmed => Fix Committed
--
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/1814373
Title:
storage / luks / dmsetup regressed
I also tested 18.04 again with another setup, still dual screen on a
samsung TV, the vlc GUI is exageratly zoomed but still correctly visible
and usable, not sure if they want it to be zoomed like that.
** Attachment added: "IdUAJtp.png"
This is confusing, I'm seeing the timeout with a TLSv1.2 connection, and
the commit pointed out in comment #9 mentions TLSv1.3.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
I can try some or all of the patches mentioned in
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1803689/comments/2
That bug might be a duplicate, btw. (or this one)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Same thing. Another, or an additional, fix is needed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1833039
Title:
18.04/Apache2: rejecting client initiated
Hi,
Thanks for report this issue.
I added a comment in commit fix that caused this regression in upstream
project:
https://gitlab.com/federicomenaquintero/bzip2/commit/74de1e2e6ffc9d51ef9824db71a8ffee5962cdbc
Soon they update there with some notes we can look for a fix. For now,
as you
I just checked and the bug is still there on 19.04.
** Attachment added: "Screenshot from 2019-06-27 20-05-31.png"
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1810346/+attachment/5273821/+files/Screenshot%20from%202019-06-27%2020-05-31.png
--
You received this bug
** Changed in: software-properties (Ubuntu)
Status: Incomplete => New
--
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/1834226
Title:
update-notifier
I can reproduce this with stock bionic (plus updates applied).
==> /var/log/apache2/error.log <==
[Thu Jun 27 19:37:43.049064 2019] [ssl:error] [pid 3084:tid 140343919978240]
[client 10.0.100.1:45036] AH02261: Re-negotiation handshake failed
It's a bit complicated to setup, as usual with SSL
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bzip2 in Ubuntu.
https://bugs.launchpad.net/bugs/1834494
Title:
latest bzip2 reports crc errors incorrectly
Status in bzip2 package in
Sorry for the late answer.
In my case, the sound was the correct one, but it was played twice at
the same time, causing some unpleasant saturation.
Furthermore, if I changed the sound in the Gnome control panel, than I
would have two different sounds playing at the same time (the newly
configure
** Changed in: policykit-1
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1828663
Title:
policykit failures due to internal user id
Bug is also present with other Nvidia Jetson packages.
https://devtalk.nvidia.com/default/topic/1056381/jetson-agx-xavier/jetpack-4-2-xavier-install-failed/post/5355851/?offset=4#5355865
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bzip2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bzip2 in Ubuntu.
** Changed in: systemd (Ubuntu Disco)
Status: New => Incomplete
** Changed in: systemd (Ubuntu Bionic)
Status: New => Incomplete
** Changed in: systemd (Ubuntu Cosmic)
Status: New => Incomplete
** Changed in: systemd (Ubuntu Eoan)
Importance: Medium => Undecided
--
You
All autopkgtests for the newly accepted systemd (229-4ubuntu21.22) for xenial
have finished running.
There have been regressions in tests triggered by the package. Please visit the
sru report page and investigate the failures.
https://people.canonical.com/~ubuntu-archive/pending-sru.html#xenial
All autopkgtests for the newly accepted systemd (229-4ubuntu21.22) for xenial
have finished running.
There have been regressions in tests triggered by the package. Please visit the
sru report page and investigate the failures.
https://people.canonical.com/~ubuntu-archive/pending-sru.html#xenial
All autopkgtests for the newly accepted systemd (229-4ubuntu21.22) for xenial
have finished running.
There have been regressions in tests triggered by the package. Please visit the
sru report page and investigate the failures.
https://people.canonical.com/~ubuntu-archive/pending-sru.html#xenial
All autopkgtests for the newly accepted systemd (229-4ubuntu21.22) for xenial
have finished running.
There have been regressions in tests triggered by the package. Please visit the
sru report page and investigate the failures.
https://people.canonical.com/~ubuntu-archive/pending-sru.html#xenial
In the updates tab, I keep all three boxes checked under "Install
updates from:", because I like to manually run `sudo apt-get update &&
sudo apt-get upgrade` whenever I have a good stable release of software
and feel like stomaching a raft of system changes.
In past versions of ubuntu going back
Hello.
It is still unclear whether this is still an issue in apt-xapian-index
or the underlying python apt bindings. I am marking this as Incomplete
for apt-xapian-index as this is still marked as affecting it and has
been since 2015, and the Trusty that was affected is End of Life.
Please
** Summary changed:
- update-notifier ignores update-manager's settings
+ update-notifier ignores software-properties's settings
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
** Changed in: software-properties (Ubuntu)
Status: New => Incomplete
--
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/1834226
Title:
update-notifier
** Changed in: curl (Ubuntu)
Status: Confirmed => Fix Released
** Tags removed: rls-ee-incoming
--
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/1832882
Title:
Good to know! Thank you!
Would it also be possible to mark the "upstream" test
(https://salsa.debian.org/systemd-
team/systemd/blob/master/debian/tests/control#L113) "flaky" or turn it
off altogether? We run it on CentOS and Arch anyway so it should be
safe. On Ubuntu CI it's particularly flaky
I tested this on an virtual machine running Eoan and did not notice
vgcfgbackup taking as much time as it doesn in an schroot.
bdmurray@clean-eoan-amd64:~$ sudo time vgcfgbackup
0.00user 0.00system 0:00.02elapsed 37%CPU (0avgtext+0avgdata 10848maxresident)k
3584inputs+0outputs
I've tried it and its not working for me. Do you need some log or
something I can try?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1833039
Title:
18.04/Apache2:
Lubuntu is suffering what seems to be a related failure although I
tracked that down to what I thought was a different upstream bug report.
In Lubuntu's case the lxqt-policykit-agent suffers a SIGSEGV as a side-
affect (I think) of polkit failing to authorise.
It was originally discovered when,
Possibly related to Bug #1821415 "pkexec fails in a non-graphical
environment"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1828663
Title:
policykit failures due to
Using gparted (which requires root access to the block storage devices)
"test" user fails whilst original "lubuntu" user is successful:
# In "lubuntu" user's GUI terminal emulator:
lubuntu@lubuntu:~$ gparted
localuser:root being added to access control list
==
libparted : 3.2
> I think it would be better to somehow address
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824864.
> arm64 has been off since December 2018 due to that issue.
yep, the ubuntu bionic kernel will be patched to increase the arm64 log buffer
size:
Also, final question, did you turn off "Download and install
automatically" for security updates?
If you only turn of "Automatically check for updates", then we won't
automatically check for updates, but if you ran apt update, the next
day-ish all updates will be downloaded automatically (it
Also, is this a desktop machine / does it have PackageKit installed, and
if so, which frontends for packagekit?
** Package changed: update-notifier (Ubuntu) => software-properties
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Hello Dan, or anyone else affected,
Accepted systemd into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.22 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Dimitri, or anyone else affected,
Accepted systemd into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.22 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
I've found that there appears to be a fundamental bug in policykit and
have added the upstream bug report covering it, which has been around
for several years but the developers don't seem able to come up with a
fix for.
Tests done using the Lubuntu 19.10 Live ISO (June 24th 2019 build) where
an
Thanks for the reports and comments. I setup a PPA with patch pointed
out by xnox in comment #7 on bionic's apache2 source package:
https://launchpad.net/~legovini/+archive/ubuntu/apache2-lp1833039
It would be great to have some feedback on the effectiveness of the
patch. Thank you!
--
You
Hello Ioanna, or anyone else affected,
Accepted systemd into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.22 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Dan, or anyone else affected,
Accepted systemd into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.22 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
You have been subscribed to a public bug:
This has been a long-standing problem with various ubuntu installations,
and I'm sensing some reticence in doing anything about it. This attitude
also seems to be purposeful to try to cajole updates on people who make
bad choices due to
** Also affects: policykit-1 (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: gitlab.freedesktop.org/polkit/polkit/issues #39
https://gitlab.freedesktop.org/polkit/polkit/issues/39
** Also affects: policykit-1 via
I'm not working on this. I filled it as a place-holder for anyone who is
willing to work on the update.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1832123
Reference:
http://changelogs.ubuntu.com/changelogs/pool/main/b/bzip2/bzip2_1.0.6-8.1ubuntu0.1/changelog
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bzip2 in Ubuntu.
https://bugs.launchpad.net/bugs/1834494
Title:
latest
Manually reverting to a previous version of /lib/x86_64-linux-
gnu/libbz2.so.1.0.4 corrects the issue for me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bzip2 in Ubuntu.
https://bugs.launchpad.net/bugs/1834494
Title:
Amr Ibrahim, are you working on this
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1832123
Title:
[SRU] Bugfix release 1.14.5
Status in gst-libav1.0 package
> looks like this has been fixed already upstream
Yes. I merged the PR (created by @yuwata) fixing that this morning.
> looks like someone stopped that; it's only running tests for 12888,
12897, and 12899 currently.
In
https://github.com/systemd/systemd/issues/12891#issuecomment-506093934 I
?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1832123
Title:
[SRU] Bugfix release 1.14.5
Status in gst-libav1.0 package in Ubuntu:
New
Status in gst-omx
Public bug reported:
I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine and
am now having problems with some .tbz2 archives. In particular, I can
no longer extract this one:
https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver-
package-31-1-0
Downloading this
> apparently something else was broken on bionic-i386 while it was off:
> https://github.com/systemd/systemd/issues/12891.
looks like this has been fixed already upstream
> In https://github.com/systemd/systemd/pull/12861#issuecomment-506025351 both
> bionic-amd64 and bionic-s390x failed due to
Yep, 1.14.4 has been released now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1832123
Title:
[SRU] Bugfix release 1.14.5
Status in gst-libav1.0 package in
** Description changed:
- When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured,
alongside many others related to systemd and gnome.
+ [Impact]
+
+ During system upgrades, triggers for gconf2 might activate too early,
+ while some of its dependencies aren't configured yet.
These fixes are also added to combined debdiff in bug 1551623.
--
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
Fix for 18.04 + build fix (bug 1834211)
this can go into bionic-proposed in one diff
** Attachment added: "Debdiff with the fix for Bionic + build fix (bug 1834211)"
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+attachment/5273780/+files/gconf-debdiff-bionic
--
You received
Now for some reason overnight, my sound settings no longer say "Dummy
Output" It says "Headphones". However, the headphones don't work. If
I open pavucontrol, it says Speakers (Unavailable) for the speakers
option.
--
You received this bug notification because you are a member of Ubuntu
Touch
I should also mention this has happened before, but I just reinstalled
Ubuntu. I'm backing everything up to do that right now, but it was
something I wanted to avoid due to the hassle. However, I'm seeing it
is becoming a bigger hassle to try to fix it without a fresh install.
--
You received
For 18.04, a build fix is required first (bug 1834211).
--
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/1551623
Title:
package gconf2 3.2.6-3ubuntu6 failed to
The attachment "Debdiff with the fix for Disco" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff. If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch"
Fix for 18.10
** Attachment added: "Debdiff with the fix for Cosmic"
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+attachment/5273779/+files/gconf-debdiff-cosmic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Fix for 19.04
** Attachment added: "Debdiff with the fix for Disco"
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+attachment/5273778/+files/gconf-debdiff-disco
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
*** This bug is a duplicate of bug 1809407 ***
https://bugs.launchpad.net/bugs/1809407
Just change your driver from proprietary to open source noveau driver. I
also had the same problem but it is solved. It is a problem of nvidia
driver.Enjoy
--
You received this bug notification because
This is similar to what happened in the past with:
- dbus (https://bugs.debian.org/771989)
- cracklib-runtime (https://bugs.debian.org/854554)
- shared-mime-info (https://bugs.debian.org/864953)
It can be fixed the same way as those. I'll post the debdiffs with the
fixes later.
** Bug watch
This bug is over a year old now, so I checked if there are news in
upcoming Ubuntu 19.10 (Eoan Ermine):
~# ip token list
token :: dev eth0
~# ip token set ::12 dev eth0
RTNETLINK answers: Invalid argument
iproute2 Version: 4.18.0-1ubuntu3
Sadly, there are none.
--
You received this bug
This bug was fixed in the package gst-plugins-base1.0 -
1.14.4-1ubuntu1.1~ubuntu18.04.1
---
gst-plugins-base1.0 (1.14.4-1ubuntu1.1~ubuntu18.04.1) bionic; urgency=medium
* No-change backport to bionic (LP: #1829366)
gst-plugins-base1.0 (1.14.4-1ubuntu1.1) cosmic-security;
This bug was fixed in the package gstreamer1.0 - 1.14.4-1~ubuntu18.04.1
---
gstreamer1.0 (1.14.4-1~ubuntu18.04.1) bionic; urgency=medium
* No-change backport to bionic (LP: #1829366)
gstreamer1.0 (1.14.4-1) unstable; urgency=medium
* New upstream bugfix release
gstreamer1.0
This bug was fixed in the package gst-python1.0 - 1.14.4-1~ubuntu18.04.1
---
gst-python1.0 (1.14.4-1~ubuntu18.04.1) bionic; urgency=medium
* No-change backport to bionic (LP: #1829366)
gst-python1.0 (1.14.4-1) unstable; urgency=medium
* New upstream bugfix release
This bug was fixed in the package gstreamer-vaapi -
1.14.4-1~ubuntu18.04.1
---
gstreamer-vaapi (1.14.4-1~ubuntu18.04.1) bionic; urgency=medium
* No-change backport to bionic (LP: #1829366)
gstreamer-vaapi (1.14.4-1) unstable; urgency=medium
* New upstream bugfix release
The verification of the Stable Release Update for gstreamer1.0 has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package gst-plugins-bad1.0 -
1.14.4-1ubuntu1~ubuntu18.04.1
---
gst-plugins-bad1.0 (1.14.4-1ubuntu1~ubuntu18.04.1) bionic; urgency=medium
* No-change backport to bionic (LP: #1829366)
gst-plugins-bad1.0 (1.14.4-1ubuntu1) cosmic; urgency=medium
* Merge
This bug was fixed in the package gst-plugins-ugly1.0 -
1.14.4-1~ubuntu18.04.1
---
gst-plugins-ugly1.0 (1.14.4-1~ubuntu18.04.1) bionic; urgency=medium
* No-change backport to bionic (LP: #1829366)
gst-plugins-ugly1.0 (1.14.4-1) unstable; urgency=medium
* New upstream bugfix
This bug was fixed in the package gst-libav1.0 -
1.14.4-0ubuntu1~ubuntu18.04.1
---
gst-libav1.0 (1.14.4-0ubuntu1~ubuntu18.04.1) bionic; urgency=medium
* New upstream bugfix release (LP: #1829366)
-- Iain Lane Thu, 16 May 2019 13:23:37 +0100
--
You received this bug
This bug was fixed in the package gst-plugins-good1.0 -
1.14.4-1ubuntu1~ubuntu18.04.1
---
gst-plugins-good1.0 (1.14.4-1ubuntu1~ubuntu18.04.1) bionic; urgency=medium
* No-change backport to bionic (LP: #1829366)
gst-plugins-good1.0 (1.14.4-1ubuntu1) cosmic; urgency=medium
*
This bug was fixed in the package gstreamer-editing-services1.0 -
1.14.4-1~ubuntu18.04.1
---
gstreamer-editing-services1.0 (1.14.4-1~ubuntu18.04.1) bionic; urgency=medium
* No-change backport to bionic (LP: #1829366)
gstreamer-editing-services1.0 (1.14.4-1) unstable;
This bug was fixed in the package gst-rtsp-server1.0 -
1.14.4-1~ubuntu18.04.1
---
gst-rtsp-server1.0 (1.14.4-1~ubuntu18.04.1) bionic; urgency=medium
* No-change backport to bionic (LP: #1829366)
gst-rtsp-server1.0 (1.14.4-1) unstable; urgency=medium
* New upstream bugfix
** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
--
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/1778844
Title:
nvme multipath does
** Changed in: fonts-noto-cjk (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to icu in Ubuntu.
https://bugs.launchpad.net/bugs/1828884
Title:
[META] Handling Japanese new era "令和
** Branch linked: lp:~rbalint/britney/autopkgtest-bionic-hint
--
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/1771858
Title:
/snap/bin not in default PATH for units, snapd
This bug also affects my company. Please integrate the fix soon.
--
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/1833671
Title:
bond interfaces stop working after restart
This bug was fixed in the package initramfs-tools - 0.131ubuntu15.2
---
initramfs-tools (0.131ubuntu15.2) cosmic; urgency=medium
* Add modules for nvme path components on multipath nvme. LP: #1778844
-- Thadeu Lima de Souza Cascardo Tue, 16 Apr
2019 21:19:25 -0300
** Changed
This bug was fixed in the package glib2.0 - 2.60.4-0ubuntu0.19.04.1
---
glib2.0 (2.60.4-0ubuntu0.19.04.1) disco; urgency=medium
* New upstream release (LP: #1832457)
+ Leak fixes to some `glib-genmarshal` generated code
+ Further fixes to the Happy Eyeballs (RFC 8305)
The verification of the Stable Release Update for glib2.0 has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
I just realised that removing chrome remote desktop config isn't enough.
Like I mentioned on my PC i had the same issue. I had to remove
.config/pulse too and restart to make it work
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Fix committed upstream:
https://gitlab.com/apparmor/apparmor/commit/7c7a4bc5311d983f2c4316252b830c52a5a0930b
and backported to apparmor-2.13.
We can work around this in qa-regression-testing or fix with an apparmor
upload.
** Changed in: apparmor (Ubuntu)
Assignee: Steve Beattie (sbeattie)
This may be relate to bug 1824753
** Package changed: gnome-control-center (Ubuntu) => qtbase-opensource-
src (Ubuntu)
** Changed in: qtbase-opensource-src (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
You have been subscribed to a public bug:
Hi
I have problem with scaling for Qt apps.
when i open Kolourpaint scaling is too small
i have Ubuntu 18.04 and install from snap and apt
i first report to bugs.kde.org and they tell me to report here
https://bugs.kde.org/show_bug.cgi?id=407668
91 matches
Mail list logo
