Package: mousepad
Version: 0.4.0-3
Severity: normal
Dear Mami Tainer,
NB: May be only tied to dconf-service (but mousepad is the only program doing
that…)
* What led up to the situation?
Open a 2nd instance of mousepad.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Open a 1st instance (command line) for editing several files,
open a 2nd instance (also from command line),
see HD access LED lit up and stay up,
failed to avoid that by adding: >/dev/null 2>&1 at the end of the opening
string,
failed to avoid that by the sacrifice of a communist lisp developer
(may be the offering was too less for the god of the HD LED),
launched iotop -oa to see that it was dconf-service that was writing to disk at
a rate of ~250KB/s.
* What was the outcome of this action?
Me unhappy,
couldn't find a way to stop that.
* What outcome did you expect instead?
mousepad &| dconf-service stop spoiling my R/W bandwidth and writing I don't
know what I don't know where.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.5.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages mousepad depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.26.0-1
ii libc6 2.22-7
ii libglib2.0-0 2.48.0-1
ii libgtk2.0-0 2.24.30-1.1
ii libgtksourceview2.0-0 2.10.5-2
ii libpango-1.0-0 1.40.1-1
mousepad recommends no packages.
mousepad suggests no packages.
-- no debconf information
