Am 06.03.2017 um 20:45 schrieb David Bremner:
> Matthias Bodenbinder writes:
>
>> Am 06.03.2017 um 13:07 schrieb David Bremner:
>>> Matthias Bodenbinder writes:
>>>
>>> Is that 32% difference with 2.2.3-1 or with 2.2.3-2?
>>>
>>> d
>&
Am 06.03.2017 um 13:07 schrieb David Bremner:
> Matthias Bodenbinder writes:
>
>>
>> I am wondering if it has to do with the fact that I am using the latest Kaby
>> Lake CPU i7-7700k?
>>
>> The Equalizer module in my case improves from 6,9 s to 3,0 s and
Am 05.03.2017 um 18:41 schrieb David Bremner:
> I'm not able to reproduce the large difference between the debian
> package and compiling with
>
> ./build.sh --disable-gnome-keyring --build-type Release
>
> On my machine (an older i7), I get an average of 40s to export with
> 2.2.3-2 (compiled w
Am 28.02.2017 um 13:25 schrieb David Bremner:
> Matthias Bodenbinder writes:
>
>>
>> I can provide DT 2 and DT 3 as deb files (approx. 9 MB each).
>>
>
> That's not needed (or helpful). But did you some place provide the
> actual benchmark you are running
Hi,
I did the comparison also with DT 2.2.3-1 from experimental and a self-compiled
binary. The result is the same:
self-compiled (opencl deactivated):
[dev_process_export] pixel pipeline processing took 14,006 secs (108,940 CPU)
binary from experimental (opencl deactivated):
[dev_process_expor
Am 20.02.2017 um 00:36 schrieb David Bremner:
> Matthias Bodenbinder writes:
>
>> And by the way, this are the commands I use to compile DT:
>>
>> ./build.sh --disable-gnome-keyring --prefix /home/software/darktable
>> --build-type Release
>> cd build
>>
To support my case I did a different benchmakr: Export 7 Canon 6D Raw to JPG
and measure the full time it takes with the "time" command.
Result:
DT 2.2.1 from debian testing repo: 1m25s
DT 2.2.1 self-combiled from debian testing source: 1m6s
DT 2.2.3 self-compiled source from DT homepage: 1m2s
-docdir=$INST/share/doc
Matthias
Am 17.02.2017 um 08:25 schrieb Roman Lebedev:
> On Fri, Feb 17, 2017 at 10:03 AM, Matthias Bodenbinder
> wrote:
>> Package: darktable
>> Version: 2.2.1-2
>> Severity: normal
>>
>> The darktable binary from debian testing is
Hello Roman,
attached are the 2 log files you where asking for.
Matthias
Am 17.02.2017 um 08:25 schrieb Roman Lebedev:
> On Fri, Feb 17, 2017 at 10:03 AM, Matthias Bodenbinder
> wrote:
>> Package: darktable
>> Version: 2.2.1-2
>> Severity: normal
>>
>&
Package: darktable
Version: 2.2.1-2
Severity: normal
The darktable binary from debian testing is very slow compared to a
self-compiled version.
1) apt-get install darktable
The darktable-cli benchmark I am using takes 22 seconds to complete
2) apt-get source darktable && compile myself
The dark
Package: src:linux
Version: 3.16.7-ckt9-3~deb8u1
Severity: normal
I have a freshly install debian jessie where systemd-udev-settle accounts for a
very long bootup time:
systemd-analyze blame:
56.397s systemd-udev-settle.service
2.735s postfix.service
482ms NetworkMan
The error also occures with the backport version 34.0-1~bpo70+1 and debian
testing.
Issue does not occur with 34.0-1~bpo70+1 and debian wheezy.
Matthias
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debi
While the segfault messages only show in the log files (seen via journalctl -f)
iceweasel prints the following messages on the console when opening a new ,
empty tab:
[Child 4077] ###!!! ABORT: LoadSheetSync failed with error 804b0012 loading
built-in stylesheet 'resource://gre-resources/ua.cs
The segfault messages appear also with all plugins and all extensions
deactivated.
Matthias
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
I downgraded iceweasel to 31.2.0esr-3 and the issue disappeared. No segfault
messages. With the same plugins. So this is obviously and issue introduced with
iceweasel 34.0-1.
Matthias
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Troubl
Package: iceweasel
Version: 34.0-1
Severity: important
When I create a new, empty tab either with cntrl-t or with the "+"-icon it get
segfault messages in the log.
For each new tab I get:Dez 05 21:37:07 rakete kernel: show_signal_msg: 2
callbacks suppressed
Dez 05 21:37:07 rakete kernel: Web Conte
Am 14.09.2014 um 18:07 schrieb Maximiliano Curia:
> ¡Hola Matthias!
>
> El 2014-09-14 a las 11:33 +0200, Matthias Bodenbinder escribió:
>
> In order to make the bug easy to test, could you please provide a simple pdf
> file where this issue is reproducible? (if the file is big,
After doing more testing I think this is more a problem with okular rather than
texmaker.
Texmaker and evince generate the exactly same printouts while okluar print outs
are stretched and misplaced.
I filed a bug report for okular a minute ago. Please close this one here.
--
To UNSUBSCRIBE,
Package: okular
Version: 4:4.14.0-2
Severity: important
When printing PDF documents okular is streching text width and text height and
additionally places the printout ca. 3mm to far to the left. This is very
annoying when printing letters generated by scrlttr2 package. (latex komascript
package)
Package: texmaker
Version: 4.3-1
Severity: normal
When printing letters created with dinbrief or scrlttr2, the foldmarks (and as
such the whole page) are ca. 3 mm too low. When using the external viewer
(okular) and printing from there, the print is correct. Which means the
foldmarks are ca. 3 mm
Hi,
I can confirm this bug. It happened to me with yesterdays dist-upgrade of
"debian testing".
Norbert's workaround with fonts.conf helped me to fix my system. I needed to
edit /etc/fonts/fonts.conf
It originaly says in line #71:
conf.d
I needed to change that to a fully qualified p
21 matches
Mail list logo
