Package: gimp
Version: 3.0.0~RC2-1
Severity: important
GIMP crashes on startup with the following segfault:
```
GNU Image Manipulation Program version 3.0.0-RC2
git-describe: GIMP_3_0_0_RC2
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=/usr/bin/cc
COLLECT_LTO_
Package: paraview
Version: 5.11.2+dfsg-6+b9
Followup-For: Bug #1065270
The issue is still present with the current version of paraview
(5.11.2+dfsg-6+b9) and libexpat (2.6.2-1), except that now downgrading
to the previous version of expat to work around the issue
is not possible anymore.
-- Syste
Package: paraview
Version: 5.11.2+dfsg-6+b1
Severity: important
Per the title, after a recent upgrade opening any data file with
appended data in 'raw' format, which was possible before the update,
fails with errors like:
vtkXMLDataParser (0x56138248c210): Error parsing XML in stream at line 27,
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 > Up
Package: bitlbee-plugin-mastodon
Version: 1.4.5-1
Severity: important
In certain circumstances that I have yet been unable to fully clarify,
the plugin segfaults (bringing down all of bitlbee with it) while processing
the timeline.
This is the relevant part of the backtrace as reported in the jou
Package: media-types
Version: 8.0.0
Severity: normal
Although the IANA registratio was apparently never finished, it is de facto
used everywhere today.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'),
Package: python3-paraview
Version: 5.10.1-2+b1
Followup-For: Bug #1010027
The bug is still present in 5.10.1-2+b1, and it affects both pvpython
and (arguably even worse) pvbatch. It seems that the command-line
options are never even read, even putting in a bogus file name like:
pvbatch nonexi
Package: nvtop
Version: 1.2.2-1
Severity: normal
Upstream has updated to version 2.0.2 that introduces support for AMD GPUs.
Would it be possibel to update the package?
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500,
Package: tt-rss
Version: 21~git20210204.b4cbc79+dfsg-1
Severity: normal
After a recent update, it seems entries can only get marked as read manually
and one by one.
Entries do not get marked as read when the link is followed,
and trying to mark all the entries in a feed as read nothing happens,
e
Package: paraview
Version: 5.9.0-2+b2
Severity: normal
File: /usr/lib/x86_64-linux-gnu/libvtkPVPythonCatalyst-pv5.9.so.1
Try got gdb a process linking to
/usr/lib/x86_64-linux-gnu/libvtkPVPythonCatalyst-pv5.9.so.1
or trying to run addr2line on it fails. gdb will just get stuck
somewhere due a sma
Package: paraview-dev
Version: 5.9.0-2+b2
Severity: normal
Trying to run paraview-config fails with:
CMake Error at
/usr/lib/x86_64-linux-gnu/cmake/paraview-5.9/vtk/VTK-vtk-module-find-packages.cmake:303
(find_package):
By not providing "FindPDAL.cmake" in CMAKE_MODULE_PATH this project
Package: libclc-12
Version: 1:12.0.1-9
Followup-For: Bug #993904
To add to this bug report, I'm getting a similer error message when trying to
use OpenCL on my machine, that has a Polaris10 card. Trying to run even just
clinfo gives the following error message:
=== CL_PROGRAM_BUILD_LOG ===
fatal
Package: kde-style-qtcurve-qt5
Version: 1.9-7+b2
Severity: normal
I noticed this while cleaning up my installation from obsolete Qt4
stuff. The breeze package recommends kde-style-qtcurve, but this leads
to the installation of kde-style-qtcurve-qt4, not kde-style-qtcurve-qt5.
Marking kde-style-qtc
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 correctly
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
Down
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
Package: fonts-symbola
Version: 2.60-1.1
Followup-For: Bug #935950
The font (and the other ancient scripts fonts) have moved to
https://dn-works.com/ufas/
An even newer version of Symbola than previously reported has
also been released. However the UFAS License under which the fonts
are released
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, even
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
Appli
Package: intel-opencl-icd
Version: 20.37.17906-1
Severity: important
Hello,
it seems that the last upgrade has broken the compilation of OpenCL
kernels, resulting in the error
unknown argument: '-dwarf-column-info'
and thus preventing use of the Intel iGP as compute device.
The error is ill
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: fi
Package: grass
Version: 7.8.2-1
Severity: important
Hello,
trying to start grass with the GUI results in the following traceback
--8<---
Launching GUI in the background, please wait...
GRASS 7.8.2 (Etna):~ > Traceback (most recent call last):
File "/usr/lib/python3.7/ctypes/__init__.
Package: ifupdown
Version: 0.8.35+b1
Severity: important
Trying to bring up any wireless interface on a network with WPA auth
fails in a very peculiar way: the interface gets correctly configured,
including WPA auth, DHCP manages to get an IP, and then an error about
failure to bring up wpa_suppli
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. So
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&#
Hello Reiner,
On Thu, Jun 20, 2019 at 11:43 AM Reiner Herrmann wrote:
> On Thu, Jun 20, 2019 at 09:30:59AM +0200, Giuseppe Bilotta wrote:
> > I came across this issue just now. This is an apparmor profile issue,
> > since by default it's configured to prevent access to local
Package: surf
Version: 2.0+git20181009-4
Followup-For: Bug #926393
I came across this issue just now. This is an apparmor profile issue,
since by default it's configured to prevent access to local files except
for a small selection (it even fails to load the corret theme in my
case).
A temporary
Package: nvidia-cuda-dev
Version: 10.0.130-1
Severity: normal
Hello,
trying to install nvidia-cuda-dev when uuid-dev is installed fails
because both packages have a '/usr/share/man/man3/uuid.3.gz' file. The
one in nvidia-cuda-dev is a symlink to the cudaDeviceProp man page
(because cudaDeviceProp
On Fri, Jan 18, 2019 at 10:45 AM Andreas Beckmann wrote:
>
> On 2019-01-18 10:19, Giuseppe Bilotta wrote:
> > Package: nvidia-cuda-dev
> > Version: 9.2.148-5
> > Severity: important
>
> > it is currently impossible to do any CUDA development and deployment i
Package: nvidia-cuda-dev
Version: 9.2.148-5
Severity: important
Hello,
it is currently impossible to do any CUDA development and deployment in
(a fresh install of) Debian testing and unstable, due to an
incompatibility between the available CUDA toolkit version and the
available NVIDIA driver ver
Package: calligra-gemini
Version: 1:3.1.0+dfsg-2+b1
Severity: normal
Installing calligra-gemini without qml-module-qtwebengine results in an
completely empty UI, with the following errors being output on console:
--8<-
file:///usr/share/calligragemini/calligragemini.qml:45:34: Ty
Package: zathura
Version: 0.3.9-1
Severity: normal
This error has appeared after an upgrade of the texlive system, which includes
a new libsynctex1. Probably zathura needs to be rebuilt against the latest
libsynctex
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
Package: surf
Version: 2.0-5
Severity: normal
Running surf triggers the following apparmor alerts:
audit: type=1400 audit(1523602672.524:7): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="/usr/bin/surf" pid=865
comm="apparmor_parser"
audit: type=1400 audit(1523606
With some further testing, it would seem that the issue of not being
able to find/access anything under that path with the intermediate
symlink affects all services,not just nfs. I'm seeing it with
git-daemon-run (which runs via runit), as well as with apache (the
gitweb site is unable to follow th
Package: nfs-kernel-server
Version: 1:1.3.4-2.1+b1
Severity: normal
I have recently changed my NFS setup so that one of the intermediate paths for
the
exported filesystem is a symlink. With this setup, trying to start the system
with
systemctl start nfs-server
fails, with `systemctl status
Package: lua-ldoc
Version: 1.4.3-5+nmu1
Severity: normal
Hello,
version 1.4.6 of lua-ldoc was released nearly a year ago (relevant tag on
GitHub: https://github.com/stevedonovan/LDoc/tree/1.4.6). It has a number of
fixes and improvements (among which, support for the --fatalwarnings command
line
Sorry for the late reply, for some reason I didn't get this message in my mail.
On Tue, 16 May 2017 15:31:47 -0500 Liam Healy
wrote:
> I believe this bug is already reported, see https://bugs.debian.org/848257.
I'm not sure it's the same bug. The java runtime warning doesn't seem
to be connecte
On Sat, May 13, 2017 at 12:42 PM, Konstantin Tokarev wrote:
> Note that there is unofficial package already:
>
> http://repo.paretje.be/unstable/#
>
> See packages libqt5webkit5, libqt5webkit5-dev
>
> Git repo of package is at
> https://gitlab.com/paretje/qtwebkit/tree/master/debian
>
> Package i
Package: libqt5webkit5
Version: 5.7.1+dfsg-1
Severity: wishlist
QtWebKit has recently restarted, due to it being faster,
lighter and more standard compliant than the Blink-derived
QtWebEngine, see e.g.
http://qtwebkit.blogspot.it/2016/08/qtwebkit-im-back.html
for the announcement (and comparison
Package: ifupdown
Version: 0.8.19
Severity: normal
I am still affected by issue #761909. Essentially, if there is a mounted nfs
share, shutdown will stall forever trying to unmount it unsuccessfully due to
the network going down before the attempted unmounting of the share. This only
happens with
Package: hdfview
Version: 2.11.0+dfsg-2+b1
Severity: important
The current version of hdfview does not show the content of any of my
HDF5 files.
Downgrading to the 2.9-3+b2 version of libjhdf{4,5}-{java, jni}, which
also installs libhdf5-8 version 1.8.13+docs-15, seems to fix the issue
for me, ev
Package: libjhdf5-jni
Version: 2.11.0+dfsg-2+b1
Followup-For: Bug #848257
I am also affected by this issue, opening an HDF5 file in hdfview results
works, but
none of the data is visible (as if the file was empty). I've done some testing
by rolling
back the versions of various packages, and it s
Package: ifupdown
Version: 0.8.13
Severity: normal
This is related to Bug#761909 (NFS not brought down during shutdown or
reboot due to the network dying too soon), which I'm still seeing on my
machine with ifupdown 0.8.13 and systemd 231-6, at least with wireless
connections (I haven't checked w
Package: zathura
Version: 0.3.6-2
Severity: wishlist
The Zathura project also provides a mupdf plugin:
https://pwmt.org/projects/zathura-pdf-mupdf/
which can be used as an alternative to the poppler-based plugin to view
PDF files.
-- System Information:
Debian Release: stretch/sid
APT prefers
sions regardless of
architecture (as long as the host compiler has a stdint.h, which it
should have since they force gcc now).
Best regards,
Giuseppe Bilotta
On Mon, May 2, 2016 at 4:04 PM, Alastair McKinstry
wrote:
> Hi,
>
> Can you point me to somewhere I can get such files (I
Hello Jerome,
> You are right.
> Meanwhile I added an entry in my TODO list concerning this package.
> I also noticed that there is two flag-file on my box: I would say that one is
> enough,
> but I cannot say more right now because I am not familiar with this part of
> the code.
> (In the past,
Hello Jerome,
On Fri, Jun 24, 2016 at 4:43 PM, Jerome BENOIT wrote:
> On 24/06/16 15:21, Giuseppe Bilotta wrote:
>> So the problem is that one of the leftover files prevented the agent
>> from starting.
>
> This is not a problem, this mechanism is meant to allow several
OK, I think I found a solution!
When I checked the permissions of my .ssh folder and all the files
within, I noticed there were a lot of leftover agent-* files in it. I
killed my manually-started ssh-agent session, removed all the leftover
files, logged out, and now the agent starts correctly when
Hello Jerome,
>> I'm using ssh 1:7.2p2-5
>
> Now I am also using ssh 1:7.2p2-5 , but I cannot still reproduce the issue.
8-/
> I suspect a bad interference with some pam_module present on your box but
> absent on mine
> and/or a privilege issue.
I will try disabling some of the less used modul
Hello,
>
> My understanding is that you have only one key, the traditional rsa key.
This is indeed the case.
> I have tried to reproduce your issue with a fake user on my box: it works
> here.
> Have you tried to start an ssh-agent by hand ?
Starting ssh-agent by hand with
eval $(ssh-agent)
a
Hello again,>> Is there anything I can do to debug the issue and
provide more information?
>
> Can you check that your current set is conform to pam_ssh(8) ?
I have not altered the pam configuration myself until now, so the
configuration is the one enabled by the package directly. greppng for
ssh
Hello Jerome,
thanks for your time
>> Not much to say: as per the title, I just found out that the latest
>> version of libpam-ssh does not launch an ssh-agent,
>
> It does on my box.
Is there anything I can do to debug the issue and provide more information?
>> even though the
>> password does
Package: libpam-ssh
Version: 2.1+ds1-1
Severity: important
Not much to say: as per the title, I just found out that the latest
version of libpam-ssh does not launch an ssh-agent, even though the
password does unlock at least one of the user keys. This is both for
local and remote logins.
-- Syste
Hello Alastair,
On Mon, May 2, 2016 at 4:04 PM, Alastair McKinstry
wrote:
> Hi,
>
> Can you point me to somewhere I can get such files (I will work with
> EUMETSAT to do so, if necessary),
>
> and some hints as to what processing you did?
Thanks for your interest in the matter. You can find a s
Package: libgrib2c-dev
Version: 1.6.0-2+b1
Severity: important
Version 1.6.0-2 (and then 1.6.0-2+b1) fail to process correctly all .grb
files in our possession (obtained by EUMETSAT). Package version 1.4.0-2
(currently in stable) works correctly on those same files..
-- System Information:
Debia
Package: libgl1-mesa-glx
Version: 11.1.3-1
Severity: normal
The glitch manifests consistently (although not in glxgears) in the form
of uniformly colored triangles covering the rendered scenes; triangles
seem to have common vertices aroung the middle of each side of the
screen, typically. The glit
Package: xserver-xorg-core
Version: 2:1.18.1-1
Severity: normal
I normally boot in console (text mode w/ KMS) and start X manually.
Today I discovered that I cannot start a second X session while the
first one is running.
Steps to reproduce:
1. boot to console (not X);
2. login;
3. start X (e.g.
Package: mah-jong
Version: 1.11-2
Severity: normal
Version 1.14 is available from te author's website.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
F
Hello Julien,
On Thu, Feb 4, 2016 at 5:17 PM, Julien Cristau wrote:
> On Wed, Feb 3, 2016 at 20:48:56 +0100, Giuseppe Bilotta wrote:
[snip]
>> Most interesting, the glitch only manifests when running on AC. If the
>> laptop is on battery, there are no issues.
>>
> Ple
Package: xserver-xorg-video-intel
Version: 2:2.99.917+git20160127-1+b1
Severity: normal
Since the upgrade to xserver-xorg 2:1.18.0-3 and
xserver-xorg-video-intel 2:2.99.917+git20160127-1+b1 I'm experiencing
the wierdest rendering corruption, which mostly manifests through a
horizontal banding of t
Package: libgit2-dev
Version: 0.23.1-1+b1
Severity: important
libgit2 depends on libhttp-parser, and libgit2-dev depends on
libhttp-parser-dev. However, the pkg-config information for libgit2 does
not include -lhttp_parser among the needed libraries, hence trying to
compile a program that depends
Package: clang-3.6
Version: 1:3.6.2-1
Followup-For: Bug #785697
I've found this happens when using the --gcc-toolchain command-line
option to choose the toolchain to use. The include path in this case is
seriously defective. Compare:
== 8< === without --gcc-toolchain =
$ echo | clang++ -x c
On Mon, Oct 12, 2015 at 10:29 AM, Giuseppe Bilotta
wrote:
> On Sun, Oct 11, 2015 at 4:39 PM, Julien Cristau wrote:
>> How exactly are you starting X? 'startx' is supposed to do the right
>> thing.
>
> I typically start with either startx or a script that does &quo
On Sun, Oct 11, 2015 at 4:39 PM, Julien Cristau wrote:
> How exactly are you starting X? 'startx' is supposed to do the right
> thing.
I typically start with either startx or a script that does "xinit
~/some-local-xinitrc", and neither works. However, I was affected by
the 227-1 systemd service
Package: xserver-xorg
Version: 1:7.7+12
Followup-For: Bug #801401
Additional information: I've added my user to the `tty` group, and while
Xorg still fails to start, the error is now different:
(EE) xf86OpenConsole: Cannot open virtual console 5 (Permission denied)
where VC5 is the next free on
Package: xserver-xorg
Version: 1:7.7+12
Severity: important
I normally boot to console and then manually launch X if/when I need it.
With the latest update to Xorg, trying to start X fails with the error
(EE) xf86OpenConsole: Cannot open /dev/tty0 (No such file or directory)
Interestingly, the
Hello
On Mon, Oct 5, 2015 at 11:15 AM, Martin Pitt wrote:
>> However, when the network is brought down (manually, or automatically
>> during system shutdown), the mountpoint is not unmounted, causing a
>> number of issues.
>
> This sounds very similar to https://launchpad.net/bugs/1492546 .
> ifu
I think I found the problem: recently part of the OpenCL ICD seems to
have been split into a separate library, which is not packaged in
Debian:
* for x86_64, libamdocl12cl64.so is needed in addition to libamdocl64.so
* for x86, libamdocl12cl32.so is needed in addition to libamdocl32.so
Package: texlive-base
Version: 2015.20150810-1
Severity: normal
The bug affects the texlive-base and/or texlive-fonts-recommended
packages currently in testing and unstable, but not in stable. In the
migration between stable and testing, the mflogo fonts was moved from
texlive-base to texlive-font
The following patch to uvm/Kbuild seems to fix the problem for me
(hoping gmail doesn't wrap it)
--- uvm/Kbuild~ 2015-06-21 15:33:08.438616334 +0200
+++ uvm/Kbuild 2015-06-21 15:33:22.662669880 +0200
@@ -219,6 +219,8 @@
RM_MODULE_SYMVERS:= $(RM_OUT_DIR)/Module.symvers
UVM_MODULE_SYMVERS:= $(obj)/M
Package: nvidia-kernel-dkms
Version: 346.72-1
Severity: important
The nvidia-uvm driver (essential to run CUDA or OpenCL programs) builds
successfully, but fails to load due missing symbols
nvUvmInterfaceSessionCreate
nvUvmInterfaceChannelAllocate
nvUvmInterfaceGetGpuArch
(etc), at least on kern
Hello,
any news about this?
On Sat, May 16, 2015 at 7:22 AM, Vincent Cheng wrote:
> Hi Giuseppe,
>
> On Fri, May 15, 2015 at 10:08 AM, Giuseppe Bilotta
> wrote:
>> Hello Vincent,
>>
>> thanks for the prompt reply!
>>
>> On Thu, May 14, 2015 at 9:49 AM
Package: tt-rss
Version: 1.15+dfsg-1
Severity: normal
Tags: patch upstream
tt-rss version 1.15 fails to import OPML feed lists, with error
DOMDocument::load(): I/O warning : failed to load external entity
"/var/cache/tt-rss/upload/opmlSR5e4i"
The error is upstream, see e.g.
https://tt-rss.
Hello,
On Fri, Jun 5, 2015 at 6:48 PM, Michael Biebl wrote:
>
> Can you please describe what kind of network setup you have and which
> tools you use to configure your network.
> How do you mount your NFS shares, is this the one listed in your fstab?
Yes, the network share is the one listed in t
Package: v86d
Version: 0.1.10-1
Severity: normal
I _think_ this has started happening with the latest kernel upgrade,
but I don't have the immediate preceding version to check. Basically,
the system boot fines, but one of my cores is stuck at 100% CPU by v86d.
-- System Information:
Debian Releas
Package: xserver-xorg-video-intel
Version: 2:2.99.917-1
Severity: normal
I've recently upgraded to the latest Xorg and Xorg intel driver in sid,
and I've noticd corrupted rendering of the terminus-oblique
font in my terminal (rxvt-unicode-256color). The problem is consistent,
in the form of missin
Hello Vincent,
thanks for the prompt reply!
On Thu, May 14, 2015 at 9:49 AM, Vincent Cheng wrote:
> Please install either nvidia 340.76-2 (sid) or 346.59-1
> (experimental), and try rebuilding the nvidia module using dkms.
It seems 346.59-1 hasn't been pushed to experimental yet? I still see 34
Package: nvidia-kernel-dkms
Version: 343.36-1
Severity: normal
I've recently upgraded the kernel on my machine to the latest
4.0.0-1-amd64 available on debian sid, and apparently the kernel side of
the nvidia driver 343.36-1 fails to build due to API differences. Might
be a good opportunity to upg
On Fri, Apr 17, 2015 at 11:16 PM, Rebecca N. Palmer
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 Haswell)?
No, ev
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 mentio
On Sat, Apr 4, 2015 at 10:30 AM, Rebecca N. Palmer
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 an Iris Pro.
> Are you
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)
a
I haven't had any issue with speed limiting and segfaults with the
latest release, I think the issue can be closed.
On Fri, Apr 3, 2015 at 5:10 PM, Sandro Tosi wrote:
> control: tags -1 + moreinfo
>
> Hello Giuseppe,
> are you able to replicate this segfault with 2.84? If so, can you
> install tr
On Wed, Apr 1, 2015 at 12:10 AM, Sandro Tosi wrote:
> Hello,
> are you still able to replicate these frequent crashes with 2.84
> uploaded in sid? If so, please run again gdb executing
I haven't seen this issue in sid recently, I think we can close the issue.
--
Giuseppe "Oblomov" Bilotta
--
Hello, I can't seem to reproduce it anymore, I think we can close this.
On Fri, Apr 3, 2015 at 5:12 PM, Sandro Tosi wrote:
> control: tags -1 + moreinfo
>
> Hello Giuseppe,
> does it still happen with 2.84?
>
> Thanks,
> --
> Sandro Tosi (aka morph, morpheus, matrixhasu)
> My website: http://matr
On Thu, Apr 2, 2015 at 6:32 PM, Onur Aslan wrote:
> Control: tags -1 wontfix
>
> On 2015-04-02, Giuseppe Bilotta wrote:
>> def FlagsForFile( filename ):
>> return { 'flags' : ['-x c'] + cppflags + cflags, 'do_cache' : False }
>
> I thin
Package: vim-youcompleteme
Version: 0+20140207+git18be5c2-2
Severity: normal
With some configurations, libclang autocompletion is not available due
to an instantaneous crash. For example, I have a (whitelisted)
.ycm_extra_conf.py structured as such:
--- 8< --
import subprocess
cppflags=subpr
Package: v86d
Version: 0.1.10-1
Severity: normal
I've recently noticed this message in my early dmesg boot:
[1.594636] v86d[160]: segfault at 7ffd29b9f3e0 ip 7f66ca1f6e64 sp
7ffc29bb02f8 error 4 in libc.so.6[7f66ca175000+19f000]
I'm honestly not sure when it started happening though
Hello,
On Mon, Nov 17, 2014 at 2:32 PM, intrigeri wrote:
>> Can you reproduce the problem (e.g. by re-installing systemd or
>> downgrading and upgrading systemd again)?
Can't seem to reproduce. We can close this bug, I'll reopen it with
more information if it reoccurs.
--
Giuseppe "Oblomov" Bi
On Wed, Nov 12, 2014 at 5:30 PM, Rebecca N. Palmer
wrote:
>> Don't quite understand this issue. How do you set the
>> OCL_STRICT_CONFORMANCE?
>
> This is Debian's beignet 0.9.3~dfsg-1 (current unstable)
> and accuracy_speed_test.py from
> https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=19;filena
On Fri, Nov 7, 2014 at 7:45 PM, Rebecca N. Palmer
wrote:
> Warning on the kernel upgrade: it froze my system, see #768483.
>
>> Ah, that's tricky, at the packaging level. What I think is:
>>
>> * all GPU-related ICDs should be installed, whenever the corresponding
>> video driver is;
>> * at least
On Fri, Nov 7, 2014 at 2:37 PM, Rebecca N. Palmer
wrote:
>> It's a Dell XPS 15 from two months ago. [...]
>> 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen
>> Core Processor Integrated Graphics Controller [8086:0416] (rev 06)
>> (prog-if 00 [VGA controller]) [...]
>> model nam
On Wed, Nov 5, 2014 at 9:33 PM, Rebecca N. Palmer
wrote:
>> Kernel: Linux 3.16-3-amd64 (SMP w/8 CPU cores)
>
> beignet doesn't work on that version of Linux (#767148); a fixed version was
> uploaded yesterday. Does upgrading to that help?
Ah, interesting. I see there's also a kernel upgrade. I'l
On Wed, Nov 5, 2014 at 8:38 PM, Andreas Beckmann wrote:
> On 2014-11-05 20:16, Giuseppe Bilotta wrote:
>> Running clinfo from http://github.com/Oblomov/clinfo with beignet installed
>
> Which other icds do you have installed?
>
> find /etc/OpenCL/vendors
I have a multitu
Package: beignet
Version: 0.9.3~dfsg-1
Severity: important
Running clinfo from http://github.com/Oblomov/clinfo with beignet installed
results in two undesired behaviours when clinfo tries to compile some
kernels:
1. the following messages are logged to stderr
: CommandLine Error: Option 'error-
Package: nvidia-smi
Version: 340.46-3
Severity: important
Something in the recent upgrades (I think starting from 340.46.2) has
made nvidia-smi unavailable on the command line. The executable is still
available under /usr/lib/#PRIVATE#, but no symlink to /usr/bin is
created. This could be related
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):
try
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 start
1 - 100 of 163 matches
Mail list logo
