Package: cage
Severity: normal
Tags: patch upstream
Dear Maintainer,
wl_touch::frame() is expected to be sent to client to indicate end of
touch frame event and not sending it may cause issues.
For example, Qt applications using Qt Wayland platform plugin do not
consider touch events until this
Package: chromium
Version: 117.0.5938.62-1~deb12u1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
chromium cannot startup after libfreetype6 upgrade to 2.12.1+dfsg-5+deb12u1.
In the latest changes of libfreetype6, macro PUT_COLOR_LAYERS_V1 was set to
NULL pointer, whic
Hi,
In chromium source code, function SkScalerContext::GlyphMetrics
SkScalerContext_FreeType::generateMetrics() will call
FT_Get_Color_Glyph_Paint() if macro TT_SUPPORT_COLRV1 exists. Somehow
FT_Get_Color_Glyph_Paint will be a NULL pointer if this patch applied, and
chromium will not be able to ru
Hi,
After apply this upgrade (2.12.1+dfsg-5+deb12u1), I cannot run chromium
(from 114 to 117) any more with segfault error. I can run chromium again if
I downgrade this package to previous version (2.12.1+dfsg-5). Maybe
chromium use this macro somewhere.
I have backported this patch and applied it to my system. Tested for more
than 2 weeks and no crashes anymore.
diff --git a/src/gallium/drivers/iris/iris_batch.c
b/src/gallium/drivers/iris/iris_batch.c
index c7a08a0e1f5f0..deab85ce4aaf3 100644
--- a/src/gallium/drivers/iris/iris_batch.c
+++ b/src/
I have backported this patch and applied it to my system. Tested for more
than 2 weeks and no crashes anymore.
diff --git a/src/gallium/drivers/iris/iris_batch.c
b/src/gallium/drivers/iris/iris_batch.c
index c7a08a0e1f5f0..deab85ce4aaf3 100644
--- a/src/gallium/drivers/iris/iris_batch.c
+++ b/src/
Package: libgl1-mesa-dri
Version: 22.3.6-1+deb12u1
Severity: normal
Tags: patch
Dear Maintainer,
Screen freeze because gnome-shell waits DRM_IOCTL_SYNCOBJ_WAIT forever in
Wayland mode when resource is tight. See
https://gitlab.freedesktop.org/drm/intel/-/issues/6851 for details.
This problem is
Package: libspice-client-gtk-3.0-5
Version: 0.35-2
Severity: normal
Once clicking into the spice-gtk widget in virt-manager, the mouse
cursor becomes invisible on the whole window (not just the VM itself)
- this includes the virt-manager main window if it's open. Clicking on
something that trigger
This bug also appears in my Debian Wheezy. I think maybe someone forgot to
catch the exception from the gtkspell if spell data is missing.
Package: src:linux
Version: 3.2.39-2
Severity: important
Dear Maintainer,
I got kernel panic randomly after I upgrade the kernel from 3.2.35 to 3.2.39-2.
I have tried to rollback the kernel to 3.2.35, and the kernel works fine again.
-- Package-specific info:
** Version:
Linux version 3.2.0-4-a
I have report the bug to freedebug.org, and the link is:
https://bugs.freedesktop.org/show_bug.cgi?id=62507
2013/3/19 SuperCat
> No, this bug occurs again just after I sent the mail. So I think maybe I
> should report the bug to bugs.freedesktop.org.
>
>
> 2013/3/19 SuperCat
&g
No, this bug occurs again just after I sent the mail. So I think maybe I
should report the bug to bugs.freedesktop.org.
2013/3/19 SuperCat
> I have tried the kernel you mentioned, and the bug also does not exist in
> this version.
>
I have tried the kernel you mentioned, and the bug also does not exist in
this version.
I tried to rollback the kernel to 3.2.35, and the bug does not occur
anymore.
Package: src:linux
Version: 3.2.39-2
Severity: important
Dear Maintainer,
The computer lags, and the X11 process has high CPU usage. I get the error
message from dmesg like:
[ 189.247399] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed...
GPU hung
-- Package-specific info:
** Vers
Package: xfwm4
Version: 4.8.3-1
Severity: normal
If you click on a dragable bar of a GTK3 application (i.e. primary toolbar /
menubar), move the window and click at a non-dragable area, the window moves
around widely without any logical direction.
You can reproduce this bug by: click on a dragab
Package: linux-2.6
Version: 2.6.32-35squeeze1
Severity: important
I updated the system by using apt-get update & apt-get upgrade today. And then
when I open the GNOME System Monitor, and then select the "Process" tab. I
found that the program will be frozen, and Kernel Oops message appeared in
17 matches
Mail list logo