** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1878076
Title:
GTK save-dialogs input-focus moves from filename to file search if a
folder is selecte
I would just like to point out that this bug persists on
Ubuntu 22.04 on unity desktop.
kernel: 5.15.0-58-generic
The folder swapping trick doesn't work. Only way to change the file name
is to copy and paste the filename written elsewhere.
--
You received this bug notification because you are a
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Released
--
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/1952191
Title:
package systemd 248.3-1ubuntu8 faile
** Tags added: originate-from-2001891 somerville
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1977986
Title:
UPower and battery indicator show update in 2 minutes when c
On Wed, Feb 8, 2023 at 10:25 AM Gunnar Hjalmarsson
<1887...@bugs.launchpad.net> wrote:
>
> That looks like a better solution indeed, and I think I have got enough
> of evidence that we should go for Sebastian's suggestion.
>
> ( Why didn't you mention that upstream discussion in your bug? ;) )
Tha
** Changed in: gtk+3.0 (Ubuntu)
Importance: Undecided => Medium
** Changed in: gtk+3.0 (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.
Out of curiosity, how did you configure a scaling factor of 1.6?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2004533
Title:
Gtk-WARNING ... drawing failure for widget .
And yes that is an inefficient way to do fractional scaling. Only Xorg
does it that way out of necessity to fit in with legacy X11. Wayland
does not need such upscaling-then-downscaling so does fractional scaling
much more efficiently than Xorg sessions.
But Nvidia's Wayland support is still sligh
Another suggestion is to use a scaling factor of 1.5 instead of 1.6.
That might simplify the required quotient to 3/2 (initially rendering at
3x resolution instead of 8x), so might be enough to have all three
monitors working.
--
You received this bug notification because you are a member of Ubun
To achieve a scaling factor of 1.6 I suspect the logic is to render at
8x resolution and then downscale 5x (because 8/5 = 1.6). And GTK has
internal size limits of 65535 in each dimension, I think. So the maximum
window size is 65535 / 8 = 8191. That should be enough to have two 4K
(3840 px) monito
Tracking upstream in https://gitlab.gnome.org/GNOME/gtk/-/issues/3050
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2004533
Title:
Gtk-WARNING ... drawing failure for wid
I think this is a consequence of your desktop being 18432 pixels wide.
Each 4K monitor is 6144 logical pixels wide because of a custom Xrandr
scaling factor of 1.6.
Turning off screens wouldn't fix it, only unplugging them might. But
still this sounds like a GTK bug because modern Nvidia GPUs like
That looks like a better solution indeed, and I think I have got enough
of evidence that we should go for Sebastian's suggestion.
( Why didn't you mention that upstream discussion in your bug? ;) )
Thanks for your persistence! I'll make that change soon.
** Changed in: gdm3 (Ubuntu)
Statu
Public bug reported:
In Ubuntu 20.04 server with HWE kernel (5.15.0-58-generic) and LXD
5.0.2, container processes are not in enforced mode as identified by aa-
status
Below are the output of aa-status in this environment.
https://pastebin.ubuntu.com/p/kT3bHSS6w7/
The problem does not occur in
I just noticed this is a shutdown crash, which isn't obvious until you
scroll down to frames #46-#54:
https://errors.ubuntu.com/problem/d31a7f723bab2a42586060136dc27f56bc71
Although that's probably not an excuse for letting this sneak into
jammy.
Another interesting note is that it looks lik
On Wed, Feb 8, 2023 at 9:15 AM Gunnar Hjalmarsson
<1887...@bugs.launchpad.net> wrote:
>
> @Hongyi Zhao: As you wrote in the duplicate bug, my simplistic code in
> comment #2, which only escapes the '<' character, would not be
> sufficient. At the same time the issue I mentioned, about --no-markup
>
@Hongyi Zhao: As you wrote in the duplicate bug, my simplistic code in
comment #2, which only escapes the '<' character, would not be
sufficient. At the same time the issue I mentioned, about --no-markup
making \n being displayed literally instead of interpreted as a newline,
still stands.
Probabl
The kinetic sbuild autopkgtest regression *looks* to be a real regression to me
- having a bit of a look, it seems mmdebstrap is checking the apt version
against
```
$content =~ /^apt ([0-9]+\.[0-9]+\.[0-9]+)[a-z0-9]* \([a-z0-9-]+\)$/m
```
while this SRU has version string "apt 2.5.3ubuntu0.1 (a
I can verify that the latest version of Ubiquity from -proposed fixes
this problem - I booted Ubuntu Desktop 22.04.1, enabled -proposed on the
ISO, installed Ubiquity from -proposed, then did a ZFS+encryption
installation. Rebooted, logged in, "sudo apt update" behaves normally,
Firefox launches an
I can also confirm that the problem persists after a fresh boot, turning
off 2 screens, and only using the main screen at 100% scale.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.ne
attached
** Attachment added: "xrandr.txt"
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2004533/+attachment/5645339/+files/xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bu
** Bug watch added: Debian Bug tracker #1030827
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030827
** Also affects: perl (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030827
Importance: Unknown
Status: Unknown
** No longer affects: perl (Debian)
** Also a
** Bug watch added: GNU Savannah Bug Tracker #63392
http://savannah.gnu.org/bugs/?63392
** Also affects: pspp via
http://savannah.gnu.org/bugs/?63392
Importance: Unknown
Status: Unknown
** Tags added: update-excuse
--
You received this bug notification because you are a member o
Hello,
I'm having the same problem on a HP ENVY x360 2-in-1 Laptop 15-ew0xxx.
The internal speaker doesn't reproduce any sound but I can use my
headset and headphone jack.
If any info is needed please do tell.
--
You received this bug notification because you are a member of Ubuntu
Touch seede
The following paragraphs are copied from the [issue
comment](https://github.com/ibus/ibus/issues/2271#issuecomment-1421247325).
I have the same problem in Ubuntu 20.04.5 LTS. I didn't have this
problem until recently (one month). I am a Chinese speaker and use
`ibus-libpinyin`. I am not a Googl
** Description changed:
+ [SRU Impact]
+
+ Sysctl was removed from 5.5 kernels. In src/test/test-seccomp.c,
test_protect_syscall
+ sysctl is called with the expectation the error result is EFAULT and not
ENOSYS.
+ This affects autotests for all focal-5.15 linux kernels (hwe, azure, gcp,
oem, g
Tagged incoming as while there is a modified casper uploaded, the
matching merge proposal was disapproved
(https://code.launchpad.net/~tsimonq2/casper/+git/casper/+merge/436490),
so the next casper upload will regress the current version of the fix.
A longer term solution is needed.
** Tags added:
*** This bug is a duplicate of bug 1933090 ***
https://bugs.launchpad.net/bugs/1933090
Thanks! I am going to copy this over to the original bug report, and
mark this as a duplicate.
** This bug has been marked a duplicate of bug 1933090
systemd/245.4-4ubuntu3.6 ADT test failure with
linux
** 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/2004640
Title:
[IOT_CPT][QCS8155.UC
** Also affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: alsa-driver (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net
** Also affects: python2.7 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: python2.7 (Ubuntu Lunar)
Importance: Undecided
Assignee: Ghadi Rahme (ghadi-rahme)
Status: In Progress
** Also affects: python2.7 (Ubuntu Bionic)
Importance: Undecided
S
The issue has been fixed upstream just before the final 2.37 release,
thus closing this.
** Changed in: libunistring (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunistring in
** Merge proposal linked:
https://code.launchpad.net/~ubuntu-core-dev/livecd-rootfs/+git/livecd-rootfs/+merge/436960
--
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/19
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/rsyslog/+git/rsyslog/+merge/436955
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1906333
I noticed that the live Lunar Ubuntu Desktop (standard Ubuntu) arrives
at a page that prompts to enter user name and password, in other words,
there is not longer a standard user with a blank password.
This should be considered when we decide how to deal with assigning a
user ID for the live sessi
Public bug reported:
To whom it may concern:
I was experiencing frequent wake-ups from s0i3x on a HP Pro 435 G9
convertible [1] using the Qualcomm FastConnect 6900 Soc [2]. The issue
is related to FW revision
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.9 that comes
bundled with Ubunt
Public bug reported:
To whom it may concern:
I was experiencing frequent wake-ups from s0i3x on a HP Pro 435 G9 convertible
[1] using the Qualcomm FastConnect 6900 Soc [2]. The issue is related to FW
revision WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.9 that comes
bundled with Ub
This module is now present in Ubuntu 22.04, so this issue can be closed.
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS"
$ dpkg-query -L rsyslog | grep pmciscoios
/usr/lib/x86_64-linux-gnu/rsyslog/pmciscoios.so
--
You
systemd error is being emitted from dispatch_notify_event() in
src/journal/journald-server.c, which is called from
server_connect_notify(). This function contains a large hunk of comment
block describing a potential race condition. I wonder if this is some
kind of race condition that only occurs o
This looks related:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1754328
--
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/1992979
Title:
kinetic ppc64le reporting
Hi saberph,
You're correct, the actual issue is not reproducible in ubuntu, but the patch
that upstream has is fixing a few memory leak issues as well along with actual
CVE fix, that's why we decided to patch this issue
--
You received this bug notification because you are a member of Ubuntu
To
41 matches
Mail list logo
