Bug#973362: Workaround

2020-10-29 Thread Bálint Kovács
Hi!

I have been afflicted by this issue too, and I have found a possible
workaround. If you boot into kernel 5.8.0-3, and run `dpkg-reconfigure
nvidia-kernel-dkms`, a usable kernel module is produced for that kenel.
Then, you can reboot or just `modprobe nvidia` and restart your X server.

Another "workaround" is upgrading to the nvidia driver packages at version
450.80.02-1, already included in sid. This implies that the bug has
thankfully been already fixed.

Bálint Kovács


Bug#929048: tracker-extract: Allocates between 5 and 10 GiB of memory when examining certain DDS files

2019-05-15 Thread Bálint Kovács
Two more things:

1. I have a few more samples in both categories, if needed

2. I do realize that this bears resemblance to #679581. However, there the 
offending process was different.

On 16 May 2019 01:42:44 BST, "Bálint Kovács"  wrote:
>Package: tracker-extract
>Version: 2.1.6-1
>Severity: critical
>Justification: breaks the whole system
>
>Dear Maintainer,
>
>   * What led up to the situation?
>I have been extracting resources from a game. When I extracted a
>handful of DDS
>files, my memory usage shot up and in about 5 seconds the entire system
>locked
>up, no moving to virtual consoles, no nothing. This kept happening,
>every time
>I logged into my profile. To investigate I killed all tracker-related
>processes.
>
>   * What exactly did you do (or not do) that was effective (or
> ineffective)?
>I have been able to identify that the misbehaving process is
>tracker-extract. I
>started running tracker-extract with an rlimit on the DDS files.
>
>   * What was the outcome of this action?
>Some files worked fine, some failed under an RLIMIT_AS of 5 GiB but not
>under
>an RLIMIT_AS of 10 GiB (but it still allocated a not insignificant
>amount of
>memory)
>
>Full output from an affected file:
>
>$ /usr/lib/tracker/tracker-extract -v 2 -f bad.dds
>00:57
>** Message: 00:57:52.901: Starting tracker-extract 2.1.6
>** Message: 00:57:52.901: General options:
>** Message: 00:57:52.901:   Verbosity    2
>** Message: 00:57:52.901:   Sched Idle  ...  1
>** Message: 00:57:52.901:   Max bytes (per file)  . 
>1048576
>(tracker-extract:9171): dconf-DEBUG: 00:57:52.901: watch_established:
>"/org/freedesktop/tracker/extract/" (establishing: 1)
>Setting scheduler policy to SCHED_IDLE
>Setting priority nice level to 19
>Loading extractor rules... (/usr/share/tracker-miners/extract-rules)
>Extractor rules loaded
>MIME type guessed as 'image/x-dds' (from GIO)
>../../../glib/gmem.c:105: failed to allocate 65687 bytes
>
>   * What outcome did you expect instead?
>Full output from an unaffected file:
>
>$ /usr/lib/tracker/tracker-extract -v 2 -f good.dds
>00:57
>** Message: 00:57:46.382: Starting tracker-extract 2.1.6
>** Message: 00:57:46.382: General options:
>** Message: 00:57:46.382:   Verbosity    2
>** Message: 00:57:46.382:   Sched Idle  ...  1
>** Message: 00:57:46.382:   Max bytes (per file)  . 
>1048576
>(tracker-extract:9113): dconf-DEBUG: 00:57:46.382: watch_established:
>"/org/freedesktop/tracker/extract/" (establishing: 1)
>Setting scheduler policy to SCHED_IDLE
>Setting priority nice level to 19
>Loading extractor rules... (/usr/share/tracker-miners/extract-rules)
>Extractor rules loaded
>MIME type guessed as 'image/x-dds' (from GIO)
>@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
>@prefix nmm: <http://www.tracker-project.org/temp/nmm#> .
>@prefix nfo:
><http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#> .
>
> a nfo:Image ,
>nmm:Photo .
>
>   * Other information
>All of the files work with imagemagick display perfectly well, they are
>even
>the same resolution.
>
>To remedy the situation, I have deleted all affected DDS files, but I
>have kept
>a tarball of an affected and an unaffected sample (along with one that
>is not
>recognized for some reason.) I have attached it to my report. Handle
>with care,
>especially if you have a desktop with tracker on it.
>
>-- System Information:
>Debian Release: buster/sid
>  APT prefers testing
>APT policy: (990, 'testing'), (500, 'testing-debug'), (500, 'unstable')
>Architecture: amd64 (x86_64)
>Foreign Architectures: i386
>
>Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
>Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
>Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
>LANGUAGE=en_US:en (charmap=UTF-8)
>Shell: /bin/sh linked to /bin/dash
>Init: systemd (via /run/systemd/system)
>LSM: AppArmor: enabled
>
>Versions of packages tracker-extract depends on:
>ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
>ii  libc62.28-10
>ii  libcue2  2.2.1-2
>ii  libexempi8   2.5.0-2
>ii  libexif120.6.21-5.1
>ii  libflac8 1.3.2-3
>ii  libgexiv2-2  0.10.9-1
>ii  libgif7  5.1.4-3
>ii  libglib2.0-0 2.58.3-1
>ii  libgsf-1-114

Bug#757166: myspell-hu: Dictionary literally empty

2014-08-05 Thread Bálint Kovács
Package: myspell-hu
Version: 1.6.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The dictionary supplied in this package is totally empty, therefore LibreOffice
reports most or all words to be incorrect. The files
/usr/share/hunspell/hu_HU.dic and /usr/share/hunspell/hu_HU_u8.dic are empty
save for a 0 and three newlines.

The problem does not appear when I compile the package from source myself.



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages myspell-hu depends on:
ii  dictionaries-common  1.23.8

myspell-hu recommends no packages.

Versions of packages myspell-hu suggests:
pn  openoffice.org  none

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org