Hi,
Seeing exactly the same bug with an Broadcom Corp. BCM2045B (BDC-2.1)
bluetooth device, so its not just the Intel AX211.
Jeremy, thanks for tracking this down!
Udo
Even more, the current 20200927 version claims in the changelog that
resynthesizer was ported to python3, but its missing entirely.
Confirming fixed in Debian 10.5 point release:
Bug is reproducible with kernel 4.19.0-9 running, not reproducible with
4.19.0-10 running. Tested via xdg-screensaver lock.
On 24.03.19 19:35, Udo Richter wrote:
I experience this behavior in most cases when light-locker kicks in as
screen saver. Closing the lid or suspending never triggers this. i965
driver on Sandybridge CPU. Ctrl-Alt-F6-F7 brings me to a
screen-is-locked display, and after some seconds
One more for the mix:
I experience this behavior in most cases when light-locker kicks in as
screen saver. Closing the lid or suspending never triggers this. i965
driver on Sandybridge CPU. Ctrl-Alt-F6-F7 brings me to a
screen-is-locked display, and after some seconds, to the actual login
Package: xpra
Version: 0.14.10+dfsg-1
Most of the video encodings for xpra are missing for me, with exception
of x264 and vpx. This affects current jessie/sid versions (0.14.9+dfsg-1
/ 0.14.10+dfsg-1) and also wheezy-backports (0.14.9+dfsg-1~bpo70+1).
I first noticed this when upgrading my
Am 01.11.2014 20:34, schrieb Dmitry Smirnov:
You need to check Session Info -- Features to check available encodings on
Server and Client. If your server runs a different version of Xpra they may
not agree on what encodings to use.
Thats why I explicitly queried the server side list of
I've made another, even more severe observation.
I'm running a rather mixed setup using lightdm, xfce4-session and kwin
as window manager, started via the session Client0_Command way.
One of the issues I recently had was a freeze at session startup,
disallowing any login unless I reverted to
Also, from reading the upstream bug report, I tried killing the dangling
at-spi processes at-spi-bus-laun and at-spi2-registr, and that fixed it
too. The processes seem to respawn after killing, and the new instances
seem to work fine for the session.
Cheers,
Udo
--
To UNSUBSCRIBE, email to
I think I'm seeing this bug too, need to check the logs later. Its
definitely some kind of oops using KVM on 3.13.
CPU: Athlon64 X2, 4Gb RAM
Kernel: linux-image-3.13-1-686-pae (3.13.10-1 and 3.13.7-1) in Jessie/i386
Bug can be avoided by booting the old 3.12 kernel.
Symptoms: Works normally, but
For reference, my oops:
INFO: rcu_sched self-detected stall on CPU { 0} (t=5250 jiffies g=7643
c=7642 q=2543)
sending NMI to all CPUs:
NMI backtrace for cpu 0
CPU: 0 PID: 5205 Comm: qemu-system-x86 Not tainted 3.13-1-686-pae #1 Debian
3.13.10-1
Hardware name: To Be Filled By O.E.M. To Be
Same here, however I'm just seeing this on the login screen (wheezy,
lightdm and gdm). Bluetooth keyboard is QWERTY, until I hit a key on the
USB keyboard (even shift), then bluetooth switches to QWERTZ, which is
default on my computer.
After that, it stays QWERTZ even if I un-plug the BT dongle
I've been on the full v11 patch for 2 1/2 weeks, no issues to report.
I've switched to the less intrusive patch now, again built on top of
3.2.0-0.bpo.1-686-pae, and I'll report on anything unusual.
As long as I don't report, you can assume that it either fused all of my
computers, or just
Am 05.04.2012 21:54, schrieb Udo Richter:
I've applied patch v8 to the source package of of 3.2.4-1~bpo60+1, and
the resulting kernel package fixed it for me too. I've just successfully
hibernated 10 times in a row, before I could hardly hibernate more than
one or two times without hanging
I've applied patch v8 to the source package of of 3.2.4-1~bpo60+1, and
the resulting kernel package fixed it for me too. I've just successfully
hibernated 10 times in a row, before I could hardly hibernate more than
one or two times without hanging.
--
To UNSUBSCRIBE, email to
It seems I am seeing the same bug too, on
linux-image-3.2.0-0.bpo.1-686-pae, 3.2.4-1~bpo60+1. However, I'm on an
nVidia nForce 570 chipset (AMD A64-x2), esp. using the sata_nv driver.
About half of the hibernate-disk cycles do work, the other half starts
writing the image to some point just
Am 27.12.2011 21:56, schrieb Ben Hutchings:
Can you test whether wake-on-LAN works with the current version in
testing (3.1.5-1)? You will need to upgrade initramfs-tools and
linux-base to install the later kernel version, but nothing else.
Seems to be working fine with 3.1.5-1, suspending to
Package: linux-2.6
Version: 2.6.32-39
Severity: normal
Tags: squeeze
Between 2.6.32-35 and 2.6.32-36, the ability to wake-on-lan from
suspend-to-disk got lost for my mainboard. Waking from poweroff and from
suspend-to-ram still works. This is probably related to bug #627700. The
bug is present up
Hi,
This is more important than whether moreblue is deprecated or not. Its
about whether desktop-base allows theme overrides or not.
/usr/share/desktop-base/grub_background.sh provides the background image
together with the font colors. And while the background image is
configurable with
Package: grub-pc
Version: 1.98+20100804-11
Severity: wishlist
Tags: patch
With the changes of bug#605705, the background can be overwritten using
GRUB_BACKGROUND in /etc/default/grub, but changing the colors of the
menu is not possible. Depending on the background, the default colors
black/black
Just wanted to add a note here:
I'm seeing a related problem here on squeeze. When going into suspend to
disk, I cannot see the suspend process console output while hibernating
or resuming. Its just plain dark for (hopefully) 30 seconds, then
switches off. After resuming however, moving the mouse
21 matches
Mail list logo
