Looks like the problem may be with the Flutter layer. What other apps
are affected?
I'm wondering if Flutter apps need a custom Nvidia sleep workaround like
bug 1876632 is about. Although that would only matter if they're using
the discrete GPU by default, and they shouldn't be.
** Package change
** Attachment added: "Screenshot from 2024-10-04 14-35-19.png"
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2077290/+attachment/5824735/+files/Screenshot%20from%202024-10-04%2014-35-19.png
** Tags removed: verification-needed-noble
** Tags added: verification-done-noble
--
You rece
Reverifying using the new method:
Installed `sudo apt install libgtk-3-0t64 -t noble-proposed`.
Got source using `apt source gtk+3.0 -t noble-proposed`
Confirmed GTK 3 version installed is 3.24.41-4ubuntu1.2.
Ran test case listed in bug description, confirmed rendering correctly
(see attached sc
This bug was fixed in the package gnome-control-center -
1:47.0.1-1ubuntu2
---
gnome-control-center (1:47.0.1-1ubuntu2) oracular; urgency=medium
* d/p/ubuntu: Add back the noble patches for recoloring the mouse animations.
Go back using css filtering since it's safer to use when
This issue was also present in this machine with Ubuntu 22.04 and I
could reproduce the behavior in other hardware.
--
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/2083650
Title
** Attachment added: "behaviour of the display"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2083650/+attachment/5824718/+files/Screencast%20from%202024-10-03%2019-29-22.webm
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
Public bug reported:
The windows contours (and shades) and display in general starts to
blinks after the computer return from the "save energy turn off of the
display".
Steps to reproduce:
- Let the display turn off and Ubuntu lock as save energy configuration;
- Wake up the computer;
- Log in;
-
** Changed in: gnome-control-center (Ubuntu)
Status: Triaged => In Progress
** Changed in: gnome-control-center (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: exiv2 (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to exiv2 in Ubuntu.
https://bugs.launchpad.net/bugs/2021929
Title:
upgrade to exiv2 0.28.0
Status in exiv2
This bug was fixed in the package newt - 0.52.24-2ubuntu3
---
newt (0.52.24-2ubuntu3) oracular; urgency=high
* d/pacthes/fix-bidi-i386.patch, d/patches/series: On i386, the build for newt
fails due to an incompatible pointer type in wchar_to_textmod_visual while
calling
fribidi
@Andrew: Simon is correct. This update deliberately had an unusual roll-
out where it went to updates first so that it could be phased, and we
could roll back if the phasing showed a problem.
The security pocket was not updated specifically to provide a users a
way to easily revert the update.
As
@Simon, thank you for the link, that also clarifies Steve's comment
(https://bugs.launchpad.net/apparmor/+bug/1597017/comments/25) earlier
in this thread which I didn't interpret appropriately during first read
through. Based on the linked thread the plan was to publish to the
security repository l
Hi, mihalicyn, sorry for the delay answering.
That's unfortunately right. Ubuntu 12.04 ships apparmor 2.7 which didn't
have support for ABIs yet, so dc757a645cfa82f6ac252365df20a36a9ff82760
causes a regression on those early versions. I talked to @jjohansen and
we have agreed that this patch needs
I agree that if /etc/ipa/ca.crt is a standard location for that package
(which appears to be
https://pagure.io/freeipa/blob/master/f/ipaplatform/base/paths.py#_69)
then we could add it to the ssl_certs abstraction
--
You received this bug notification because you are a member of Ubuntu
Touch seed
@Andrew, I think publishing to -updates first and then to -security was
intentional per https://discourse.ubuntu.com/t/upcoming-apparmor-
security-update-for-cve-2016-1585/44268/3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
I am running Focal Fossa and noticed that AppArmor was vulnerable
(CVE-2016-1585). My automatic upgrade attempts were not upgrading from
the vulnerable version 2.13.3-7ubuntu5.3build2 to the latest version
2.13.3-7ubuntu5.4. When investigating further it is because my systems
are configured to only
This bug was fixed in the package python-docker - 5.0.3-1ubuntu1.1
---
python-docker (5.0.3-1ubuntu1.1) noble; urgency=medium
* Remove use of distutils to fix import error. (LP: #2061929)
- d/p/remove-distutil.patch: eliminate distutils in credentials.
- d/p/use-packaging.pa
My takeaway from the above is that the daemon service itself still runs
as root, just the group name changes, so for the specific scenario
raised in question #2 it looks like the daemon's read access to root
only files like shadow would be unaffected. Similarly, the issue I
raised in "Where Proble
A. sasl2 not installed:
$ apt-cache policy sasl2-bin
sasl2-bin:
Installed: (none)
Candidate: 2.1.28+dfsg1-5ubuntu3.2~oracular1
Version table:
2.1.28+dfsg1-5ubuntu3.2~oracular1 500
500
https://ppa.launchpadcontent.net/bryce/cyrus-sasl2-sru-lp2078851/ubuntu
noble/main amd64 Pac
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware. I recommend
performing a back up and then investigating the situation. Measures you
might take include check
Public bug reported:
Automatic response, don't know anything about it. Triggered during
installation.
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: libcups2t64 2.4.7-1.2ubuntu7.2
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
ApportVersion
*** This bug is a duplicate of bug 2083509 ***
https://bugs.launchpad.net/bugs/2083509
** This bug has been marked a duplicate of bug 2083509
Screen freeze
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu
Public bug reported:
System Freeze.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: pass
CompositorRun
Switching back to "new" since the fix still needs to be added to the
Ubuntu package.
** Changed in: apparmor (Ubuntu)
Status: Fix Committed => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
htt
This bug was fixed in the package libgdata - 0.18.1-8
---
libgdata (0.18.1-8) unstable; urgency=medium
* Team upload
* Backport patch to drop GTimeVal usage (LP: #2083528)
* Add proposed patch to fix build on 32-bit time_t architectures
* Add Build-Depends: ca-certificates for
** Description changed:
- I have upgraded to the oracular beta yesterday on my home machine. After
- upgrading I started to notice errors issued by libgio that MOUNT_2_40
- could not be found despite having libmount1 2.40.2 installed as part the
- upgrade.
+ In April 2024, while handling the t64 t
I am marking this bug as invalid, since this seems related to systemd
reload instead and not a dbus issue.
** Changed in: dbus (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubu
This is most likely a mesa issue. Have you upgraded mesa recently to
match when it showed up?
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in
I am glad that it was a specific case. I was holding off updating any
other machines to oracular for fear of having to go through the same
thing. I had not realised that t64 packages were temporary and were all
replaced with other versions later. As I said before, I will be carrying
out an audit of
Then I guess it confirms the hypothesis we had, you most probably had
the bad luck of updating/upgrading during the time frame the package
came with libmount1t64 in proposed back in April.
I will try to summarize this in the bug description to help anyone else
who ended up in this situation, feel
** Changed in: apparmor (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2083612
Title:
aa-remove-unknown: I/O error for unconf
This was fixed upstream with
https://gitlab.com/apparmor/apparmor/-/merge_requests/1240
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2083612
Title:
aa-remove-unknown: I
Yes, the machine in question is a test machine which gets updated once
the beta comes out. The update to noble was no different and like this
upgrade, I had upgraded around a month before actual release.
At the time due to the XZ debacle, I had also had to use proposed with a
pin priority of 500 t
Looking at a machine that was upgraded to noble past the release date, I
have no t64 packages installed at all. On the test machine I remember
having around 5 such t64 packages getting installed at the time. I will
check again to see if there are any still lingering around and replace
them with the
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2081684
Title:
Things depending on libmount1 complain MOUNT_2_40 not found
Status in uti
Public bug reported:
On a stock ubuntu 24.04.1 install, running sudo aa-remove-unknown logs
"/usr/sbin/aa-remove-unknown: 112: echo: echo: I/O error" for every
unconfined profile it encounters.
I've reproduced this on an Azure stock image with apparmor
4.0.1really4.0.1-0ubuntu0.24.04.3. It matche
> Couldn't work out why they aren't updating automatically but manually
> installing the .debs shows the
> issue fixed, thanks!
Thanks Robert for your verification, but could you please expand on what
verification steps you actually performed, and with which package versions? The
instructions
We kept digging in the publishing history and we have an hypothesis.
Did you upgrade to noble before the release (maybe sometimes between 2024-04-18
and 2024-04-23)?
Do you use the proposed pocket?
During the t64 transition and the rebuild/republish of some packages
just prior the release maybe
> This I believe trigger a systemd-networkd restart
Do you have logs showing the link between dbus being updated and systemd
restarted?
Does something similar happen when you just reinstall dbus?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, w
the autopkg test regression is not caused by binutils, but by the newer gcc
13.3.0 version.
This is reported in LP: #2081797, and needs an adjustment in the kernel
packages.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bi
checked the build logs that the flags are passed
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils
All autopkgtests for the newly accepted binutils (2.42-4ubuntu2.3) for noble
have finished running.
The following regressions have been reported in tests triggered by the package:
linux-ibm/6.8.0-1013.13 (amd64)
Please visit the excuses page listed below and investigate the failures,
proceedin
Public bug reported:
I can't watch a video for long time, the background music keep fading,
and make me feel nausea
Tried many different configurations online, reinstall alsa, pulseaudio,
disable pipewire, lastly tried to install wireplumber following this
link
https://discourse.ubuntu.com/t/blu
This seems related to
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2003250
--
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/2083489
Title:
Upgrading dbus tear down ne
Could it be that there is no new version of libmount1t64 and that
libmount1 has no "Replaces:" for libmount1t64?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2081684
Ti
Additional note: `gdbus` is how Flutter finds out the OS preference for
animations, and therefore whether to skip (fast-forward) animations or
not. That means that all Flutter apps that hit this issue will skip
animations. I originally filed an issue against Flutter SDK here:
https://github.com/flu
Public bug reported:
Last week, I did a clean install of Ubuntu 24.04 LTS on a relatively
beefy Thinkpad. This is going to be my Linux build machine (for a game
I'm working on) so I installed only a few things: VSCode, Steam,
Caffeine, Timeshift, and the requirements for building the game (Flutter
Note: this bug report was filed from the clean install VM using `ubuntu-
bug`. But if it helps, I can also report from my (non-VM) linux machine
if it helps. That installation is not as clean as the VM.
I also have a clone of the VM before I upgraded it to the latest
version, if that helps. The is
Thanks for the detailed explanation.
I believe the issue was then due to the interrupted upgrade process. The
system probably ended up in a undefined state. Moreover I do not think I
can reasonably reproduce.
There is most likely nothing wrong with the packages.
I am marking it as Invalid and w
Dear Mr. Mars,
Thank you for your reply.
I had upgraded directly from noble a day after the oracular beta was
released.
I started the process using "do-release-upgrade" (due to past issues
with the graphical updater) but for some reason, my lock screen
triggered (I should have ran the upgrade in
Hello borgdylan,
I understand the similar issue in arch was caused by glib2 2.80 being
built against a version of util-linux not yet published. I understand it
was fixed when `util-linux-2.40rc2-1` was made available.
In our case, I checked that our current version of glib2
(https://launchpad.net
** Package changed: xorg (Ubuntu) => gnome-settings-daemon (Ubuntu)
** Also affects: gnome-session (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://b
52 matches
Mail list logo
