I'm sorry to hear about your upgrade troubles. If you have logs from the
the boot where the upgrade occurred, please open a different bug with
those logs so that the root cause for the hang can be investigated.
But, if you unplugged your machine during the upgrade because it was
unresponsive, I am
The patch mentioned in #3 solved the issue for system boot with UFS
storage
** Changed in: oem-priority
Status: New => Confirmed
--
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.l
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2046844
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
** Changed in: kalgebra (Ubuntu)
Status: Triaged => Fix Released
** Changed in: marble (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.la
All of these apparmor profiles appear to be broken on live sessions for
seeded applications, e.g. kalgebra and marble on Edubuntu and digikam on
Ubuntu Studio.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu
I have checked with Security Team and they advice that it is a bit late
in the cycle to make a significant change in the behaviour. Would it be
possible to obtain Feature Freeze Exception[1] for the issue if you
would like it to be included in Oracular, or resubscribe Sponsors early
in the next rel
The attachment "rust-cargo-c-minor-fix.debdiff" seems to be a patch. If
it isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned b
** Changed in: marble (Ubuntu)
Status: Fix Released => Triaged
** Changed in: marble (Ubuntu)
Milestone: ubuntu-24.04-feature-freeze => ubuntu-24.10
** Changed in: kalgebra (Ubuntu)
Status: Fix Released => Triaged
** Changed in: kalgebra (Ubuntu)
Milestone: ubuntu-24.04-fea
Thanks for reporting this. I can reproduce as well. It appears this was
fixed upstream in https://github.com/systemd/systemd/pull/31683.
It should already be fixed in Oraculr, but we will backport this to
Noble.
** Also affects: systemd (Ubuntu Noble)
Importance: Undecided
Status: New
You have been subscribed to a public bug:
When my screen blanks from inactivity timeout the backlight stays on,
for multiple hours and does not turn off ever.
Additional Notes:
* "Everything else" appears to be working fine. I can move my mouse, enter
password on lock screen, and resume doing w
Liu,
The best practices around Rust vendoring are still a work-in-progress.
It is an interesting technique to use a second .orig tarball to contain
the vendoring. I used a different method when I vendored gnome-snapshot.
Because workflows are not standard yet, could you add a
debian/README.source
** Package changed: ubuntu => xorg (Ubuntu)
--
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/2081244
Title:
External Monitor backlight does not turn off on blank
Status in xor
Hi Jeremy,
Please find the refinement in the patch attached.
** Patch added: "rust-cargo-c-minor-fix.debdiff"
https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/2078055/+attachment/5819451/+files/rust-cargo-c-minor-fix.debdiff
--
You received this bug notification because you are a memb
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to librsvg in Ubuntu.
https://bugs.launchpad.net/bugs/2078055
Title:
librsvg needs cargo-c but it's not available on i386
Status in librsvg package in Ubuntu:
Triaged
Status in
Public bug reported:
I have a Dell monitor connected to my Lenovo X1 Carbon Yoga (Gen 6).
There is an invisible line where, if I hold my mouse 'on' this line, the
Lenovo screen shakes. It does not shale all the time and it seems to be
linked to the website I am displaying on the Lenovo screen. For
I still got this problem for an upgrade to 24.04 done yesterday (by a
relative - I just spent 3 hours on the phone trying to fix the machine).
Looking at https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/2055012 (marked as a duplicate of this bug), this bug is
still affecting other p
This bug was fixed in the package ubuntu-settings - 24.04.5
---
ubuntu-settings (24.04.5) noble; urgency=medium
* debian/control: Update vcs references to noble branch
* Set default background in GDM gnome-initial-setup session.
Use ubuntu default background when using the GNO
This bug was fixed in the package ubuntu-advantage-tools - 34~24.04
---
ubuntu-advantage-tools (34~24.04) noble; urgency=medium
* Backport 34 to noble (LP: #2075543)
ubuntu-advantage-tools (34) oracular; urgency=medium
* d/rules: check that version.py is consistent with changelo
This bug was fixed in the package ubuntu-advantage-tools - 34~22.04
---
ubuntu-advantage-tools (34~22.04) jammy; urgency=medium
* Backport 34 to jammy (LP: #2075543)
ubuntu-advantage-tools (34) oracular; urgency=medium
* d/rules: check that version.py is consistent with changelo
This bug was fixed in the package ubuntu-advantage-tools - 34~20.04
---
ubuntu-advantage-tools (34~20.04) focal; urgency=medium
* Backport 34 to focal (LP: #2075543)
ubuntu-advantage-tools (34) oracular; urgency=medium
* d/rules: check that version.py is consistent with changelo
This bug was fixed in the package apparmor -
4.0.1really4.0.1-0ubuntu0.24.04.3
---
apparmor (4.0.1really4.0.1-0ubuntu0.24.04.3) noble; urgency=medium
* Revert to version 4.0.1-0ubuntu0.24.04.2 except for the patch
that enables the bwrap-userns-restrict profile (LP: #2072811).
This bug was fixed in the package apparmor -
4.0.1really4.0.1-0ubuntu0.24.04.3
---
apparmor (4.0.1really4.0.1-0ubuntu0.24.04.3) noble; urgency=medium
* Revert to version 4.0.1-0ubuntu0.24.04.2 except for the patch
that enables the bwrap-userns-restrict profile (LP: #2072811).
The verification of the Stable Release Update for procps has completed
successfully and the package is now being 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 r
This bug was fixed in the package procps - 2:4.0.4-4ubuntu3.1
---
procps (2:4.0.4-4ubuntu3.1) noble; urgency=medium
* d/sysctl.d/10-bufferbloat.conf: set default qdisc to fq_codel (LP:
#2003027)
-- Heitor Alves de Siqueira Wed, 17 Jul 2024
14:59:18 +
** Changed in: procps (
Indeed, but we have a new SRU being prepared which will include the fix,
I will try to get that uploaded today or tomorrow
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie-preferences in
Ubuntu.
https://bugs.launchpad.
Sometimes this also appears:
/usr/lib/python3/dist-packages/gi/overrides/Gtk.py:1694: Warning: g_object_ref:
assertion 'G_IS_OBJECT (object)' failed
return _Gtk_main(*args, **kwargs)
(update-manager:188833): Gdk-CRITICAL **: 11:19:39.154: gdk_window_get_display:
assertion 'GDK_IS_WINDOW (wind
After some whack-a-moling, removing the setBusy calls from
toggle_from_items makes the issue go away, as does removing
while Gtk.events_pending():
Gtk.main_iteration()
from setBusy().
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packa
Public bug reported:
GUI not starting after login. But startx works after login on tty )ctrl-
alt-f3)
ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.11.0-7.7-generic 6.11.0-rc7
Uname: Linux 6.11.0-7-generic x86_64
ApportVersion: 2.30.0-0u
Running apport-retrace -g /var/crash/_usr_bin_update-manager.1000.crash:
#0 0x7d4ee9769649 in g_type_check_instance_is_fundamentally_a () from
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
[Current thread is 1 (Thread 0x7d4eea231080 (LWP 113728))]
(gdb) bt
#0 0x7d4ee9769649 in g_type_check_
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
an
** Attachment added: "system-journal.png"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2081170/+attachment/5819300/+files/system-journal.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager
there's no upload for this on the noble queue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie-preferences in
Ubuntu.
https://bugs.launchpad.net/bugs/2065294
Title:
Diagnostics settings flips to Never without any u
Public bug reported:
This issue happens only in Ubuntu Core 24.
When trying to create a connection using nmcli in the network-manager
snap, it will raise an Error showing failed to add connection but
actually the wwan connection is successfully created.
System journal shows that libnetplan.so.1
** Attachment added: "create-gsm-fail.png"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2081170/+attachment/5819299/+files/create-gsm-fail.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manag
This error is coming from systemd-sysusers in systemd.postinst. To
isolate the failing call, can you share the output of:
$ SYSTEMD_LOG_LEVEL=debug systemd-sysusers basic.conf systemd-
journal.conf systemd-network.conf
Looking at the code, this is either failing on an open() or flock(), so
likely
** Changed in: gnome-online-accounts
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1871019
Title:
Nextcloud account added
It appears to be a known issue that WSL1 does not support F_OFD_SETLKW,
which is what systemd is using here. I could add a fallback to use
F_SETLKW instead, but according to [1], it sounds like the locking is
just broken on WSL1? So the "fallback" would probably lead to even more
issues.
Do you ge
root@drenec:~# SYSTEMD_LOG_LEVEL=debug systemd-sysusers basic.conf
systemd-journal.conf systemd-network.conf
Locking /etc/.pwd.lock failed: Invalid argument
Failed to take /etc/passwd lock: Invalid argument
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
** Tags removed: rls-jj-incoming
** Tags added: foundations-todo
--
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/2077159
Title:
i40e interfaces renamed after upgrade from h
Public bug reported:
In one of my working unit (service), I try to toggle the MemoryKSM
boolean setting.
Using any of:
MemoryKSM=yes
MemoryKSM=on
MemoryKSM=true
MemoryKSM=1
Results in:
Sep 19 16:16:56 systemd[1]: Started XXX.service - XXX service.
Sep 19 16:16:56 (e_server)[4487]: XXX.service:
By default, the NamePolicy=[1] (as configured in
/usr/lib/systemd/network/99-default.link) is:
[Link]
NamePolicy=keep kernel database onboard slot path
This means that if the kernel claims to assign a predictable name, then
that will take precedence over other policies, including the "onboard"
po
Re-adding a Linux task to see if anyone can confirm whether kernel
interface naming was changed between these two kernel versions.
--
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/b
The previous gnome-control-center SRU failed verification (bug 2072772).
We're now synchronizing this upload with a fixed version of the previous
upload.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie-preferences in
This bug was fixed in the package apparmor -
4.0.1really4.0.1-0ubuntu0.24.04.3
---
apparmor (4.0.1really4.0.1-0ubuntu0.24.04.3) noble; urgency=medium
* Revert to version 4.0.1-0ubuntu0.24.04.2 except for the patch
that enables the bwrap-userns-restrict profile (LP: #2072811).
This bug was fixed in the package apparmor -
4.0.1really4.0.1-0ubuntu0.24.04.3
---
apparmor (4.0.1really4.0.1-0ubuntu0.24.04.3) noble; urgency=medium
* Revert to version 4.0.1-0ubuntu0.24.04.2 except for the patch
that enables the bwrap-userns-restrict profile (LP: #2072811).
The verification of the Stable Release Update for ubuntu-settings has
completed successfully and the package is now being 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 enc
This bug was fixed in the package ubuntu-advantage-tools - 34~16.04
---
ubuntu-advantage-tools (34~16.04) xenial; urgency=medium
* Backport 34 to xenial (LP: #2075543)
ubuntu-advantage-tools (34) oracular; urgency=medium
* d/rules: check that version.py is consistent with change
This bug was fixed in the package ubuntu-advantage-tools - 34~18.04
---
ubuntu-advantage-tools (34~18.04) bionic; urgency=medium
* Backport 34 to bionic (LP: #2075543)
ubuntu-advantage-tools (34) oracular; urgency=medium
* d/rules: check that version.py is consistent with change
** Merge proposal linked:
https://code.launchpad.net/~nteodosio/update-manager/+git/update-manager/+merge/473514
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/2041831
This bug was fixed in the package modemmanager - 1.20.0-1~ubuntu22.04.4
---
modemmanager (1.20.0-1~ubuntu22.04.4) jammy; urgency=medium
* Apply the newer modemmanager commits from 1.22.0 to the LTS as part of
new hardware enablement including Quectel EM061K-GL/EM160/RM520N modem
The verification of the Stable Release Update for modemmanager has
completed successfully and the package is now being 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 encoun
Thank you for your bug report. That's not a bug in the Ubuntu package,
could you submit it there instead https://github.com/snapcore/network-
manager-snap/issues
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member o
Thank you Luís for taking the time to open this ticket, and respond with
the additional logs. I am from the from the kernel team, and I have
looked over the dmesg.log that you have provided.
I don't see any networking issues in the kernel log relating to the kernel, but
I do see that some Virtua
Hi Jorge , thank you for taking the time to open this bug report!
I've gone over the kernel logs, and nothing in the kernel logs indicate
a kernel issue.
I see the bluetooth device set up, and functioning, and then later
systemd is called to stop and restart the device, which also doesn't git
any
54 matches
Mail list logo
