[Bug 2049315] Re: cups-browsed running non-stop on two cores
Hi Till,
I've tried running this test in a loop:
```
while { echo 3; echo N; echo; } | run-tests.sh; do true; done
```
With the new version of cups-browsed from -proposed, it ran 14
iterations until failure (i.e., until a nonzero exit status). However,
with the old version of cups-browsed, it still failed, but after 141
iterations. So I don't really know how to interpret this or if this
difference is significant. It seems unideal that the test inevitably
fails for me regardless of which version I am testing!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049315
Title:
cups-browsed running non-stop on two cores
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2049315/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2086587] Re: Random flickering with Intel i915 (Comet Lake and Kaby Lake) on Linux 6.8+
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-noble-linux ** Tags added: verification-done-noble-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2086587 Title: Random flickering with Intel i915 (Comet Lake and Kaby Lake) on Linux 6.8+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049315] Re: cups-browsed running non-stop on two cores
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 cups-browsed service caught in a 100% loop in under 15 minutes on two different machines (this script will fail to restart the service after it gets stuck, so the service will be stuck at 100% CPU where it can be easily observed until it is SIGKILL'd). Then, *after* upgrading to the package in -proposed, I have been running this script on two machines for over six hours without it getting stuck on either. ** Tags removed: verification-needed-noble ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049315 Title: cups-browsed running non-stop on two cores To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2049315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2023380] Re: hardware decoding not working although does for mpv
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 Title: hardware decoding not working although does for mpv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/2023380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2086587] Re: Random flickering with Intel i915 (Comet Lake and Kaby Lake) on Linux 6.8
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: Onboard IGD Subsystem: Dell UHD Graphics 620 [1028:081c] Kernel driver in use: i915 The 6.8.0-48 kernel had not fixed the flicker issue for me, but this one does. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2086587 Title: Random flickering with Intel i915 (Comet Lake and Kaby Lake) on Linux 6.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on Linux 6.8
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 another patch that encompasses a greater array of affected hardware. -- 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: Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on Linux 6.8 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2062951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on Linux 6.8
> 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:5917] (rev 07) DeviceName: Onboard IGD Subsystem: Dell UHD Graphics 620 [1028:081c] Kernel driver in use: i915 -- 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: Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on Linux 6.8 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2062951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on Linux 6.8
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062951 Title: Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on Linux 6.8 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2062951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on Linux 6.8
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: Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on Linux 6.8 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2062951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049315] Re: cups-browsed running non-stop on two cores
> 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 we never set eol. > > The function expects as input a string terminated by a linefeed. But the > parameter line = "Content-Security-Policy" has no linefeed. We should not > rely on web-servers providing well formed responses. I think we have to rethink what is happening here a bit. In gdb, after hitting the infinite loop, I investigated the underlying file descriptor by printing `http->fd` and then matching it with what was outputted by `lsof`. I found a surprising discovery -- the file descriptor in use wasn't an Internet socket -- it was a Unix domain socket! I suspect the infinite loop we are hitting is from cups-browsed querying `/run/cups/cups.sock`. I believe that your debugging above Heinrich supports this hypothesis as well, since "Content-Security-Policy" is one of the headers returned by `/run/cups/cups.sock`. I am curious if you can reproduce my finding. For me, this was an unexpected discovery because if my analysis is correct then (1) I don't think we can easily blame buggy network printers for what is happening (but maybe the cups server is buggy?) and (2) I also don't think we can explain the nondeterminism behind this bug by appealing to random network errors, since this issue is occurring over a Unix domain socket and not (e.g.) a dodgy WiFi connection. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049315 Title: cups-browsed running non-stop on two cores To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2049315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on Linux 6.8
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 of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062951 Title: Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on Linux 6.8 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2062951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04)
> 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 UHD Graphics 620 [8086:5917] (rev 07) DeviceName: Onboard IGD Subsystem: Dell UHD Graphics 620 [1028:081c] Kernel driver in use: i915 -- 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: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2062951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04)
> 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 Ubuntu. https://bugs.launchpad.net/bugs/2062951 Title: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2062951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04)
> 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 issue. The commit enables the following compile time kernel config options: CONFIG_INTEL_IOMMU_DEFAULT_ON=y CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON=y These enable the Intel IOMMU by default (although it can still be disabled by the linux command line at runtime via Grub). For completeness here is the corresponding commit in the noble kernel: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/noble/commit/?id=77e530c1a864c601b96622db03bc1f38e51155f1 > What about the fact that the issue also affect upstream/mainline > kernels? I don't know how the kernel config values for the mainline builds that I linked to were derived, but in the build that I tried (built July 25 2024) the above config options were also enabled. I don't know if this is because the upstream kernel has now enabled these config options by default or if the builds that I linked to still use custom Ubuntu config options. > Are you trying to say that the issue is just related to the conditions > described in the commit and intel_iommu=igfx_off? Specifying intel_iommu= on the linux command line is a way of overriding at runtime whatever is specified by the CONFIG_INTEL_IOMMU_DEFAULT_ON config option when the kernel is compiled. Specifying intel_iommu=off would be the way to completely undo the config changed by the problematic commit, but since the bug that we are experiencing only (to my knowledge) affects graphics, I figured that intel_iommu=igfx_off would be more conservative workaround, as it only disables Intel's integrated graphics from going through the IOMMU but otherwise keeps the IOMMU enabled. It's not exactly clear to me what the benefits of having graphics going through the Intel IOMMU are, but if Intel's IOMMU was only enabled recently in Ubuntu kernels then I just assume that I won't miss whatever those benefits are. -- 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: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04)
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/unstable/commit/?id=14ebfcacaeb07b02235f2ea881fd6e34e3de0d6f The commit text reads: > UBUNTU: [Config] enable Intel DMA remapping by default > BugLink: https://bugs.launchpad.net/bugs/1951440 > > We have tried in the past to enable CONFIG_INTEL_IOMMU_DEFAULT_ON and > CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON (starting with Jammy), but > there were multiple issues (especially with old hardware), so we ended > up disabling these options afterwards, see LP: #1971699. > > Considering that IOMMU is enabled by default in upstream kernels, > probably most of these issues are solved now (or old hardware has been > decommissioned). > > Moreover, having this enabled by default can prevent potential issues > with modern hardware and drivers (see for example LP #1958004). > > Acked-by: Philip Cox > Acked-by: Andrei Gherzan > Signed-off-by: Andrea Righi The commit text even predicts that the commit may introduce problems with older hardware. Its predictions appear unfortunately accurate. Operating under the assumption that this commit introduced the bug, as a workaround, I have found that adding: intel_iommu=igfx_off to the GRUB_CMDLINE appears to resolve the issue for me. Unfortunately, there appears to be no relief in the newest kernels. I tried the latest daily build available here: https://kernel.ubuntu.com/mainline/daily/ ...and found that the issue still persists there with the default GRUB_CMDLINE. -- 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: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956040] Re: Malformed TLS handshake with OpenSSL 3.0 (breaks subversion)
@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: Malformed TLS handshake with OpenSSL 3.0 (breaks subversion) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/serf/+bug/1956040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960280] Re: subverion's svn fails against https servers
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 against https servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/1960280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956040] Re: Malformed TLS handshake with OpenSSL 3.0 (breaks subversion)
** 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 bug go to: https://bugs.launchpad.net/ubuntu/+source/serf/+bug/1956040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956040] [NEW] Malformed TLS handshake with OpenSSL 3.0 (breaks subversion)
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, breaks when using the https protocol. For instance, the command... svn info https://svn.apache.org/repos/asf/subversion/trunk ... will no longer work and, depending on the server, may close the connection or return some sort of error. Attempting to analyze the problem in wireshark, I discovered that the TLS traffic generated by libserf is malformed and cannot be parsed by wireshark's packet disassemblers. At a glance, it appears that libserf is sending a raw TLS Client Hello without first sending a TLS record header. For instance, to use the illustrated handshake example here [1], the handshake that libserf generates appears to be missing the first five bytes (the TLS record header) and instead begins with what the illustrated example calls the TLS handshake header. [1] https://tls.ulfheim.net/ ** Affects: serf (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/1956040 Title: Malformed TLS handshake with OpenSSL 3.0 (breaks subversion) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/serf/+bug/1956040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1320022] Re: [Dell Latitude E6540] ALPS touchpad keeps having state reset
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1320022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1258837] Re: [Dell Latitude E7440] ALPS touchpad keeps having state reset
Ø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 the relevant change.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1258837 Title: [Dell Latitude E7440] ALPS touchpad keeps having state reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 907640] Re: alt-backtick doesn't work properly
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 doesn't work properly To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/907640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 907640] Re: alt-backtick doesn't work properly
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/907640 Title: alt-backtick doesn't work properly To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/907640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 907640] Re: alt-backtick doesn't work properly
** 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 about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/907640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1258837] Re: [Dell Latitude E7440] ALPS touchpad keeps having state reset
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 Ubuntu. https://bugs.launchpad.net/bugs/1258837 Title: [Dell Latitude E7440] ALPS touchpad keeps having state reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1258837] Re: [Dell Latitude E7440] ALPS touchpad keeps having state reset
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 bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1258837 Title: [Dell Latitude E7440] ALPS touchpad keeps having state reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1258837] Re: Dell Latitude E7440 ALPS touchpad keeps having state reset
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 touchpad to stop working for a few moments, but typically avoiding spurious movement and clicking. This will also cause your dmesg logs to look like this instead: [ 2571.411451] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 [ 2571.411456] psmouse serio1: issuing reconnect request [ 6112.042246] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 [ 6112.042260] psmouse serio1: issuing reconnect request . . . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1258837 Title: Dell Latitude E7440 ALPS touchpad keeps having state reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1101903] Re: Constantly rising memory usage by gnome-panel
** 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1101903 Title: Constantly rising memory usage by gnome-panel To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-panel/+bug/1101903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 907640] Re: alt-backtick doesn't work properly
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 out and log back in again to make sure metacity is using the new setting. -- 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 about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/907640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 907640] Re: alt-backtick doesn't work properly
** 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/907640 Title: alt-backtick doesn't work properly To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/907640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 780602] Re: nm-applet leaks memory and stops functioning after a while
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.net/bugs/780602 Title: nm-applet leaks memory and stops functioning after a while To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/780602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 780602] Re: nm-applet leaks memory and stops functioning after a while
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 merged yesterday, in case they are substantially different from the *ubuntu3 packages you had before. ** Attachment added: "valgrind.log" https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/780602/+attachment/3442947/+files/valgrind.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/780602 Title: nm-applet leaks memory and stops functioning after a while To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/780602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 780602] Re: nm-applet leaks memory and stops functioning after a while
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 iterations, but I have > 50 wifi networks visible in my menu at the moment, so it might take others many more iterations if we think that's relevant. During running the script, if you open the nm-applet menu, you should see it flickering madly. (Sometimes the script will stall for a few seconds due to a dbus timeout --haven't debugged this yet, gah...) I can't reproduce it using this spam script running under valgrind though, probably due to valgrind's performance penalty (the menu doesn't visibly flicker when I run the script). I'll try to get a valgrind log the more natural way by just letting it run, which hopefully will still take ~24-48 hours, assuming I don't have to reboot for anything in the meantime. ** Attachment added: "spam.py" https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/780602/+attachment/3442434/+files/spam.py -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/780602 Title: nm-applet leaks memory and stops functioning after a while To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/780602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 780602] Re: nm-applet leaks memory and stops functioning after a while
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 described in the original bug description. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/780602 Title: nm-applet leaks memory and stops functioning after a while To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/780602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 946171] Re: Authentication dialog window loses focus easily - Ubuntu 12.04
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.launchpad.net/bugs/946171 Title: Authentication dialog window loses focus easily - Ubuntu 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-gnome/+bug/946171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 946171] Re: Authentication dialog window loses focus easily - Ubuntu 12.04
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 think metacity is buggy, feel free to find/create another report about that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/946171 Title: Authentication dialog window loses focus easily - Ubuntu 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-gnome/+bug/946171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 946171] Re: Authentication dialog window loses focus easily - Ubuntu 12.04
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 test it and report your feedback. I also tried to upload a 12.10 test package, but launchpad yelled at me since it's essentially the same package as the 12.04 package modulo the changelog (12.10 hasn't changed the package yet since 12.04). But quantal users can still test it by manually adding the precise repository, or by manually installing one of the debs here: http://ppa.launchpad.net/jeff250/ppa/ubuntu/pool/main/p/policykit-1-gnome/ I'm also attaching the debdiff patches. ** Patch added: "Proposed debdiff for precise" https://bugs.launchpad.net/ubuntu/+source/policykit-gnome/+bug/946171/+attachment/3238967/+files/policykit-1-gnome_0.105-1ubuntu4.precise.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/946171 Title: Authentication dialog window loses focus easily - Ubuntu 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-gnome/+bug/946171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 946171] Re: Authentication dialog window loses focus easily - Ubuntu 12.04
** 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 to Ubuntu. https://bugs.launchpad.net/bugs/946171 Title: Authentication dialog window loses focus easily - Ubuntu 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-gnome/+bug/946171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 946171] Re: Authentication dialog window loses focus easily - Ubuntu 12.04
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 ** Bug watch added: GNOME Bug Tracker #676076 https://bugzilla.gnome.org/show_bug.cgi?id=676076 ** Also affects: policykit-gnome via https://bugzilla.gnome.org/show_bug.cgi?id=676076 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/946171 Title: Authentication dialog window loses focus easily - Ubuntu 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-gnome/+bug/946171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
