I just upgraded a core system from Ubuntu 18.04->20.04->22.04, and this
is somehow the only system that has this 2minute + wait bug.
How exactly was this not handled automatically in the upgrade process
for 20.04->22.04? Isn't that the whole point of that automation?
I'm not entirely sure right
** Summary changed:
- Unable to setup Google Online Accounts with Nvidia drivers
+ GTK internal browser does not render with Nvidia drivers
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/2023322
Title:
Unable to setup Google Online Accounts with Nvidia drivers
Status in
Public bug reported:
I don't known, but the system report the bug
ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: openssh-server 1:9.0p1-1ubuntu8.5
ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
Uname: Linux 6.2.0-34-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture:
*** This is an automated message ***
This bug is tagged needs-packaging which identifies it as a request for
a new package in Ubuntu. As a part of the managing needs-packaging bug
reports specification,
https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-
packaging bug reports
I just realised it happens when I'm change from 60hz to 120hz. Doesn't
mean in 120hz my monitor crash, just when I make a change in my display,
sometimes the desktop makes that strange glitch.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Public bug reported:
The server fails to start its network with DHCP seemingly randomly. It
can take a few reboots to bring up the network. This causes issues where
automated updates that trigger a reboot cause the server to go offline.
I've attached syslog examples of both success and failure.
If you find a way to reproduce it, for example installing into a VM in such
a way that you can trigger it, then it would be helpful. The point is that
there are millions of standard Ubuntu installs involving a few different
kernel versions and the only reports of it are a couple here. If a
I'm experiencing the same issue as well.
I'm using an Asus TUF A15 with an RTX 4050.
Gnome crashes when using multiple screens with Firefox and the file
explorer.
One tip is to debug 'the frozen screen' by changing the screen order in
Settings > Display.
Best regards,
--
You received this
This bug was fixed in the package ubuntu-release-upgrader - 1:23.04.7
---
ubuntu-release-upgrader (1:23.04.7) lunar; urgency=medium
* do-release-upgrade: pass XDG_CURRENT_DESKTOP env var (LP: #2034986)
* Run pre-build.sh: updating po files, mirrors, and demotions.
-- Nick
The verification of the Stable Release Update for ubuntu-release-
upgrader 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
The attachment "modemmanager-1.20.6-1ubuntu2.patch" 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
*** This bug is a security vulnerability ***
Public security bug reported:
There are two CVEs with a score of 9.8 CRITICAL published on 29-08-2023:
* https://nvd.nist.gov/vuln/detail/CVE-2023-40889
* https://nvd.nist.gov/vuln/detail/CVE-2023-40890
No new release seems to be available that
** Also affects: samba (Ubuntu)
Importance: Undecided
Status: New
** Changed in: samba (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
@Michael: Then you hadn't installed version version 1:23.04.7 of ubuntu-
release-upgrader first, right? Please compare comment #44.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
I tested network-manager 1.44.2-1ubuntu1.1 inside a Mantic LXD
container. Package installation/upgrade and Netplan migration of (valid)
connection profiles worked nicely, according to the "Test Plan":
# Previous version of NM is installed
root@mm-nm-sru:~# dpkg -l network-manager
** Patch added: "modemmanager-1.20.6-1ubuntu2.patch"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/2039611/+attachment/5710761/+files/modemmanager-1.20.6-1ubuntu2.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Hi I am seeing this issue `search DOMAINS` on Ubuntu jammy arm64 in the
following environment.
```
$ cat /etc/os-release | grep ^VERSION
VERSION_ID="22.04"
VERSION="22.04.2 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
$ uname -m
aarch64
$ dpkg -S /etc/network/if-up.d/resolved
ifupdown:
Just now upgrading ubuntu-mate 23.04 to 23.10 and encountered the
corrupt text issues. Screenshot attached.
** Attachment added: "corruption.png"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2034986/+attachment/5710737/+files/corruption.png
--
You received this
Am in the process of an Ubuntu-Mate 23.04 to 23.10 upgrade and have the
corrupted text issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986
Title:
some text
** Changed in: openssh (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2000276
Title:
FIDO2 user verification impossible when using
It's an upstream GNOME issue and landed a fix recently, see details on
https://bugzilla.redhat.com/show_bug.cgi?id=2240490 , it should be
included in the 45.1 updates
** Bug watch added: Red Hat Bugzilla #2240490
https://bugzilla.redhat.com/show_bug.cgi?id=2240490
** Package changed: gtk+3.0
Same here on a French keyboard.
In a Wayland session, softwares such as Gedit, Thunderbird or Libre
Office are unable to display accented capiatals using caps-lock (but
VSCode works fine). In an X11 session everythings works as expected.
--
You received this bug notification because you are a
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gtk+3.0 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
** Changed in: ntp (Ubuntu)
Status: Invalid => Confirmed
** Tags added: needs-packaging
** Changed in: ntp (Debian)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
Hello Steve, or anyone else affected,
Accepted network-manager into mantic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.44.2-1ubuntu1.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
** Package changed: ubuntu => wayland (Ubuntu)
** Package changed: wayland (Ubuntu) => mutter (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/2039660
Title:
You have been subscribed to a public bug:
After upgrading to 23.10 from 23.04, I am unable to input accentuated
caps chars like « É ».
STR:
- Configure keyboard input as french (any variant does the job it seems)
- Make sure you are in caps lock mode
- Type the "2 é" char on the keyboard
As noted in #57, this bug _does_ occur on standard desktop installs,
such as mine (updated from 21.10 to 22.04, thus taking firefox from .deb
to snap).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
After restoring git history for bug #2038439 I've now uploaded this SRU
into Mantic, using the `ubuntu-mantic` branch (tag:
ubuntu/1.44.2-1ubuntu1.1):
https://launchpad.net/ubuntu/mantic/+queue?queue_state=1_text=network-
manager
** Description changed:
[ Impact ]
* A failure to query
ok- I just saw I needed to mark the bug as Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2037906
Title:
[Intel AX201] Bluetooth LE not working after upgrade from
Is there anything else I can provide?
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2037906
Title:
Public bug reported:
I have attempted every possible fix that I could find online, but Pulseaudio
and Ubuntu Sound Settings fails to set 7.1 surround sound audio when it's
selected. I have my 7.1 surround sound system connected through ARC connection
on my television. While Windows and other
Thanks for the bug report. Can you explain in more detail where and when
you see the error?
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
** Summary changed:
- Nwidia driver Ubuntu bug
+ Nvidia driver Ubuntu bug
** Package changed: ubuntu
** Summary changed:
- [amdgpu] Screen artifacts/UI oddities on Wayland following Steam/Proton
session
+ [amdgpu] Screen artifacts/UI oddities on Wayland
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: mesa (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2038998
Title:
[amdgpu] Screen
Also just in case you've found a new form of bug 2034619 please try
adding this to /etc/environment:
MUTTER_DEBUG_KMS_THREAD_TYPE=user
and then reboot.
** No longer affects: ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Package changed: xorg (Ubuntu) => 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/2039391
Title:
pakage broken
Status in Ubuntu:
Incomplete
Bug description:
There's also a lot of this in the journal:
GNOME Shell crashed with signal 11
so to help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
2. If step 1
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Also affects: nvidia-graphics-drivers-535 (Ubuntu)
Importance: Undecided
Status: New
** Tags added: nvidia suspend-resume
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
*** This bug is a duplicate of bug 2034619 ***
https://bugs.launchpad.net/bugs/2034619
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 2034619, so it is being marked as such. Please
Also reported in:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7062
** Package changed: xorg (Ubuntu) => mesa (Ubuntu)
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #7062
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
(SRU team member): It's not entirely clear to me what the status of this
bug is? It's marked as verification-done and all the autopkgtests are
clear, but there's a lot of “it doesn't work” chatter. Let's see if I
can summarise:
Werner seems to be seeing a hanging problem with 249.11-0ubuntu3.11.
nice.
http://www.hairvitamins6.com
http://www.uaegoldpricetoday.com
http://www.saudigoldpricetoday.com
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/145604
Title:
VRGB
great work.
http://www.hairvitamins6.com
http://www.uaegoldpricetoday.com
http://www.saudigoldpricetoday.com
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/164640
Title:
very good post.
http://www.hairvitamins6.com
http://www.uaegoldpricetoday.com
http://www.saudigoldpricetoday.com
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1639372
Title:
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
50 matches
Mail list logo