Looks good! Using 6.8.0-51, I disabled the `intel_iommu=igfx_off`
workaround and reproduced the flicker. I then installed 6.8.0-53 from
noble-proposed and failed to reproduce the flicker, even though the
`intel_iommu=igfx_off` workaround was still disabled.
** Tags removed: verification-needed-n
Thanks Timo. I have tested the noble package from the -proposed
repository using the following script:
```
#!/bin/sh
while true; do
service cups-browsed restart
printf .
sleep 15s
done
```
On two different machines, *before* upgrading to the package in
-proposed, this script got the
There is now a commit addressing this in vlc 3.x upstream:
https://code.videolan.org/videolan/vlc/-/commit/ba5dc03aecc1d96f81b76838f845ebde7348cf62
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2023380
Thanks, before testing I disabled the intel_iommu= workaround, and this
kernel does indeed fix the flicker issue for me.
For reference this is my hardware:
$ lspci -nnk | grep -A3 VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620
[8086:5917] (rev 07)
DeviceName: O
Hi @rebbel, the kernel version you cite is the "fixed" version, but it
does not include a fix for *all* affected hardware. Since you have
already provided in comment 116 the hardware info that AceLan requested,
you have done everything you need to at this time. Hopefully AceLan can
soon prepare a
> If adding "intel_iommu=igfx_off" works for you, but you still encounter the
> flicker issue with 6.8.0-48.48,
> please attch your gfx info here, thanks.
>lspci -nnk | grep -A3 VGA
$ lspci -nnk | grep -A3 VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620
[8086
4. Or per comment 73 your CPU/GPU is affected by this issue but is not
yet covered by the patch in 6.8.0-48? I'm hoping AceLan can chime in
concerning what hardware is covered by the patch and what is still
planned.
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
The proposed kernel does not fix the issue for me, but maybe this is
expected? AceLan, does the workaround include Kaby Lake R CPUs yet?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062951
Title:
> We are in function httpGets() which seemingly has been called with parameter
> line being a NUL terminated string "Content-Security-Policy".
>
> We cycle in the loop 'while (lineptr < lineend)'.
> http->used = -47
> bufptr > bufend
> *lineptr = "Content-Security-Policy"
>
> As bufptr > bufend w
Hi Adam,
I believe there are different flickering bugs affecting different
processors at this time. Does the `intel_iommu=igfx_off` workaround
work for you? That would go toward understanding whether you are
affected by #2062951.
--
You received this bug notification because you are a member o
> And in this bug, we are trying to fix the flicker issue that can be worked
> around by intel_iommu=igfx_off
> I'll need your VGA PCI ID if intel_iommu=igfx_off works for you.
>lspci -nnk | grep -A3 VGA
$ lspci -nnk | grep -A3 VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation U
> model name : Intel(R) Core(TM) Ultra 7 155H
Hi Sean, this processor does not appear to have a Gen9 GPU. You are
likely experiencing another bug. You may consider opening a new bug
report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
> Thank you for doing your research into the issue but I am confused by
> your results.
>
> Are you claiming that removing mentioned Ubuntu specific commit resolves
> the issue?
Specifically it's the first commit where I experience the bug, so I
would assume that reverting it will resolve the iss
Despite some of the nondeterminism behind this bug, I believe I have
bisected this bug to the following commit in the Ubuntu kernel tree:
14ebfcacaeb07b02235f2ea881fd6e34e3de0d6f .
More info is available on this commit here:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/unsta
@schopin This curious patch appears to fix subversion in my use cases,
and it looks like wireshark can disect the TLS traffic again too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956040
Title:
I believe that this bug is a duplicate of this one:
https://bugs.launchpad.net/ubuntu/+source/serf/+bug/1956040
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960280
Title:
subverion's svn fails aga
** Tags added: transition-openssl3-jj
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956040
Title:
Malformed TLS handshake with OpenSSL 3.0 (breaks subversion)
To manage notifications about this bu
Public bug reported:
This bug is a regression in libserf-1-1 version 1.3.9-10ubuntu1, which
switched to OpenSSL 3.0. Version 1.3.9-10, which uses OpenSSL 1.1, does
not have this bug.
Using version 1.3.9-10ubuntu1, Subversion, which is the only dependant
of this package in the Ubuntu repository,
** Changed in: linux (Ubuntu)
Status: Expired => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1320022
Title:
[Dell Latitude E6540] ALPS touchpad keeps having state reset
To manag
Øyvind, I experienced that when I upgraded to BIOS A10 from A08.
Fortunately, I was able to downgrade from A10 back to A08. I suspect
that either A10 has an issue or it just pokes even harder at this bug
than A08 did. (A10 cites "Keyboard input improvement" as one of its
fixes, which is probably
Dimitri, I use metacity in saucy/trusty via gnome-session-flashback, so
shouldn't the bug/patch be valid for trusty as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907640
Title:
alt-backtick
Here's a debdiff incorporating the proposed patch.
** Patch added: "Proposed debdiff for trusty"
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/907640/+attachment/3954813/+files/metacity_2.34.13-0ubuntu4.debdiff
--
You received this bug notification because you are a member of Ubunt
** Also affects: metacity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907640
Title:
alt-backtick doesn't work properly
To manage notifications
There's no actual regression though because, although the generic mouse
driver doesn't have the sync issue, using it is even worse since it
doesn't expose any touchpad-specific functionality.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Allan, do the older kernels that don't seem to exhibit the bug recognize
the touchpad as a touchpad? For instance, with the older kernels that
don't seem to exhibit the bug, does the 'xinput' command list a generic
mouse instead of what's normally listed as your touchpad?
--
You received this bu
This sync issue with the E7440 touchpad can cause spurious clicks too.
One thing that I found helps is to add psmouse.resetafter=1 to
GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub (and then run update-
grub and reboot).
This will cause the driver to reset when it loses sync, causing the
touchpa
** Also affects: gnome-panel via
https://bugzilla.gnome.org/show_bug.cgi?id=688967
Importance: Unknown
Status: Unknown
** Bug watch added: GNOME Bug Tracker #688967
https://bugzilla.gnome.org/show_bug.cgi?id=688967
--
You received this bug notification because you are a member of
I've filed a metacity bug upstream with a proposed patch.
In the meantime, as a workaround, if your gconf setting for
/apps/metacity/global_keybinds/switch_group is 'Above_Tab', then
try setting it to 'grave' (ensure a lowercase 'g'), assuming the
key above your tab key is a backtick. Then log ou
** Bug watch added: GNOME Bug Tracker #692437
https://bugzilla.gnome.org/show_bug.cgi?id=692437
** Also affects: metacity via
https://bugzilla.gnome.org/show_bug.cgi?id=692437
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ub
Thanks Alex. Unfortunately, after ~24 hours, I still see the
nonresponsive menu entries and the empty menus with your patched version
of the appmenu-gtk* packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Alex, I'm attaching my valgrind log from running nm-applet for about ~18
hours, terminating with SIGINT when I saw the empty menu lists failing
the [Test Case]. This log was generated *without* running my spam
script. This log was generated running the *ubuntu2.1 packages from the
bzr branch merg
Alex, yes, I've installed all *.deb from build-area.
I'm attaching a python spam script that I modified from the examples
network-manager comes with that can reproduce the issue for me in ~1
minute by repeatedly adding and deleting a connection via dbus. I see
the bug appear after about 500 itera
Alex, thanks for taking a stab at this. I've built and installed the
0.9.4.1-0ubuntu3 packages from your bzr branch, and then I rebooted.
Unfortunately, after running for ~24 hours, I can still reproduce the
unresponsive menu entries and empty "More networks" and "VPN
Connections" menus that are d
I've tested the precise-proposed package on three different installs,
and the issue appears resolved.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
policykit-gnome presently uses stale timestamps to focus the password
dialog--it should use a timestamp that is as fresh as the user input
that triggered its focus.
Maybe metacity should be more forgiving with buggy application-provided
timestamps, but this report is about policykit-gnome. If you
I see that issue with nautilus too, but I believe that is a separate
bug, although it may be similar in source.
I've uploaded a test policykit-1-gnome package for 12.04 to my ppa here:
https://launchpad.net/~jeff250/+archive/ppa
Please upgrade the policykit-1-gnome package, log out, log in, and t
** Patch added: "Proposed debdiff for quantal"
https://bugs.launchpad.net/ubuntu/+source/policykit-gnome/+bug/946171/+attachment/3238968/+files/policykit-1-gnome_0.105-1ubuntu4.quantal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
I've submitted the bug upstream with a possible patch to fix it. I believe
that this bug is related to metacity's focus-stealing prevention and use of
stale X11 timestamps to activate windows. Please see the upstream bug for more
details:
https://bugzilla.gnome.org/show_bug.cgi?id=676076
** B
38 matches
Mail list logo
