Package: inkscape
Version: 1.2.2-2+b1
Followup-For: Bug #1034289
Additional information: the issue I'm seeing seems to match upstream
issue #3664
https://gitlab.com/inkscape/inkscape/-/issues/3664
and seems to be related to a GTK bug when GTK_IM_MODULE=xim
Unsetting the variable or testing one of
Package: inkscape
Version: 1.2.2-2+b1
Severity: serious
Adding or editing a text box causes the canvas to stop updating
altogether. Writing, selecting, etc still works, but the canvas does not
refresh anymore until Inkscape is closed and reopened.
This is also with the Preferences > Rendering >
On Wed, Sep 22, 2021 at 8:32 AM Andreas Beckmann wrote:
> So if it does matter abi-wise for intel-opencl-icd which version of llvm
> libigfoo1 was compiled against, we should model this in the dependency
> chain.
To be able to confirm this, I would need a version of all the libig*
stuff
Package: intel-opencl-icd
Followup-For: Bug #994833
Downgrading ONLY intel-opencl-icd to version 20.44.18297-1 leads to a
different error:
Abort was called at 41 line in file:
/build/intel-compute-runtime-7vSeZ9/intel-compute-runtime-20.44.18297/shared/source/built_ins/built_ins.cpp
Aborted
e is present also when intel-opencl-icd is the only installed
ICD.
I used to be able to use the ICD without issues on this machine. I'm not
sure which upgrade broke it (in particulr, I'm not sure if this was
broken by an upgrade of this package or by a kernel upgrade).
Cheers,
Giuseppe Bilotta
h libigc1 and
libigdfcl1 at version 1.0.5353.1-2 and indeed both bugs seem to be
fixed.
(I'd be wary of the code still calling abort in case of issues,
though, since an ICD should just fail “properly” when things go wrong
during init.)
Thanks a lot,
Giuseppe Bilotta
--
Giuseppe "Oblomov" Bilotta
Package: intel-opencl-icd
Followup-For: Bug #974702
Some additional information: I have tried downgrading to previous
versions of the package, and I found out that:
intel-opencl-icd 20.13.16352-1 has the issue
intel-opencl-icd 20.02.15268-1 has not
In fact, with 20.02 clinfo at least works,
Package: intel-opencl-icd
Version: 20.37.17906-1
Severity: critical
When this package is installed, any OpenCL program will abort with the
message
Abort was called at 42 line in file:
/build/intel-compute-runtime-WsWnhf/intel-compute-runtime-20.37.17906/shared/source/built_ins/built_ins.cpp
Package: linux-headers-amd64
Version: 5.6.14-2
Severity: serious
Try to upgrade linux-headers-amd64, linux-image-amd64 and linux-perf to
version 5.7.6-1 results in the following errors:
Preparing to unpack .../15-linux-headers-amd64_5.7.6-1_amd64.deb ...
dpkg-maintscript-helper: error:
Package: cycle
Version: 0.3.1-16
Followup-For: Bug #940902
I'm experiencing this issue as well. For debugging purposes, I moved the
previous .cycle directory out of the way, created a new user, saved, and
on restart it asked me to create a new user again —despite having
created the new profile.
of indent vs 1 tab for
two levels, which is not supported in Python3.
Best regards,
Giuseppe Bilotta
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'oldoldstable'), (500, 'unstable'), (500
On Fri, Apr 17, 2015 at 11:16 PM, Rebecca N. Palmer
rebecca_pal...@zoho.com wrote:
now every kernel invocation, regardless of arguments
counts and array sizes, fails
i.e. including ones that worked in 1.0.2-1?
Yes.
Do they use the 'local' memory
space (which triggers a third known bug on
Hello,
I've finally had time to test the latest version in experimental
(1.0.2-2) and now every kernel invocation, regardless of arguments
counts and array sizes, fails with
drm_intel_gem_bo_context_exec() failed: Invalid argument
so I might be among the ones affected by the other bug you
On Sat, Apr 4, 2015 at 10:30 AM, Rebecca N. Palmer
rebecca_pal...@zoho.com wrote:
The ICD interface works for me (i5-3230M), which makes this bug _both_
hardware- and interface-dependent, which is weird.
The other person that I'm in contact with and whose machine exhibits
the same problem has
Package: beignet-opencl-icd
Version: 1.0.2-1
Severity: grave
Tags: upstream
Since version 1.0.1 beignet has been able to recognitze the hardware on
my machine
00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core
Processor Integrated Graphics Controller [8086:0416] (rev 06)
Package: kate
Version: 4:4.14.2-1
Severity: grave
Trying to upgrade to kate 4:4.14.2-1 on amd64 fails due to:
Preparing to unpack .../kate_4%3a4.14.2-1_amd64.deb ...
Unpacking kate (4:4.14.2-1) ...
dpkg: error processing archive
/var/cache/apt/archives/kate_4%3a4.14.2-1_amd64.deb (--unpack):
Package: pavucontrol
Version: 2.0-2
Followup-For: Bug #765725
I'm experiencing the same error, consistently, when Chromium is running
and on a WebRTC-enabled page. For example, start Chromium, enable WebRTC
support, go to http://appear.in/linux and accept to share webcam and
microphone. Then
Package: gcc-4.8
Version: 4.8.1-4
Severity: serious
gcc-4.8 and related packages are at different versions in sid on amd64
(4.8.1-5) and i386 (4.8.1-4), but the same version _must_ be installed
for all architectures. This prevents upgrading of gcc-4.8 and all
related packages on multiarch (amd64
Thanks for the reply. However, I do believe this is still a bug in the
dependency specification, since if the hdf5-tools
package depends on the *latest* version of the libhdf5-1.8 package,
then it should explicitly do so, to prevent installation
when the correct version cannot be installed
Package: hdf5-tools
Version: 1.8.8-6
Severity: grave
The binaries in this version of hdf5-tools are linked against
libhdf5.so.7, but the package depends on libhdf5-1.8 that provides
libhdf5.so.6. Therefore, all of the tools fail to launch with:
error while loading shared libraries: libhdf5.so.7:
Package: infinoted-0.5
Version: 0.5.0-1
Severity: grave
Trying to install the package fails becase the postinst script tries to set up
an alternative for infinoted-0.4.1 instead of -0.5 ; the prerm script has a
similar
issue with 0.3. It looks lik they are the ones for the wrong version.
--
2009/3/24 Sebastian Dröge sl...@circular-chaos.org:
Which version of libavcodec52 do you have installed?
Package: libavcodec52
New: yes
State: installed
Automatically installed: yes
Version: 4:0.5.svn20090318-0.0
Priority: optional
Section: libs
I dist-upgraded today to the latest debian
Package: cheese
Version: 2.24.3-1
Severity: grave
Justification: renders package unusable
Loading cheese fails with the (console) message:
---
ERROR: Caught a segmentation fault while loading plugin file:
/usr/lib/gstreamer-0.10/libgstffmpeg.so
Please either:
- remove it and restart.
- run with
23 matches
Mail list logo
