Bug#881177: closed by Hilmar Preuße (Re: Bug#881177: xdvi does not draw all the symbols properly)

[Leon Meier]

No, sorry I don't know. And to be honest: I don't really care. The most
important information for me is that it is fixed in the latest version
and I therefore don't have to care any more.

Sorry,
   Hilmar


Alright, no problem, thanks anyway!!!

Leon.

Bug#881177: xdvi does not draw all the symbols properly

[Leon Meier]

Hi Hilmar,

I cannot reproduce this problem using xdvi on ubuntu disco as of today 
(2019-08-01).  I'll double-check the current status on Debian later and 
report here.


Cheers,
Leon

Bug#885153: how to reproduce

[Leon Meier]

Embarrassingly for me, I made some typos in the how-to-reproduce 
description. The (hopefully) typo-free version is below:

--

1) Make sure that /tmp does NOT contain a file named test.txt
2) Create /tmp/Test if not present
3) Create a symlink /tmp/Test/test.txt -> ../test.txt
4) Notice that the symlink is dangling, i.e., not pointing anywhere
5) Run fslint-gui /tmp/Test
6) Click on "Bad symlinks", make sure that "Dangling" is selected, and
click on "Find"
7) Observe the error message ": ord()
expected a character, but string of length 11 found".

Bug#885153: fslint-gui won't find dangling symlinks

[Leon Meier]

Package: fslint
Version: 2.44-2

How to reproduce in Debian stable:

1) Make sure that /tmp does NOT contain a file named test.txt
2) Create /tmp/Test
3) Create a symlink /tmp/Test -> ../test.txt
4) Notice that the symlink is hanging, not pointing anywhere
5) Run fslint-gui /tmp/Test
6) Click on "Bad symlinks", make sure that "Dangling" is selected, and 
click on "Find"
7) Observe the error message ": ord() 
expected a character, but string of length 11 found".


The program fslint-gui errored on a directory containing dangling symlink.

What should have been done instead is displaying which symlink is broken 
(here: /tmp/Test/test.txt). This bug turns into a huge problem when you 
run fslint-gui on huge directories: you could derive that a dangling 
symlink probably exists, but you don't know where it is exactly.


Any bugfix?

Thanks in advance
Leon

Bug#880665: "transfered" is wrong, but not complained about

[Leon Meier]

On 21.12.2017 13:25, Rene Engelhard wrote:

reassogn 880665 hunspell-en-us



You probably wanted to say "reassign", not "reassogn"...

Bug#880665: "transfered" is wrong, but not complained about

[Leon Meier]

Package: libreoffice-writer
Version: 1:5.2.7-1

How to reproduce:

1. Open a fresh document.
2. Type in "transfered".
3. Mark the word as English (USA).
4. Run the spellchecker.

Observe that no complaints are issued.
However, the correct form has double "r", namely "transferred".
So, the spellchecker must complain.

(I'm not reporting upstream, since I don't know who is the culprit: the 
flexion mechanism, the dictionary, or libreoffice itself.)

Bug#880203: After suspend, cpufreq/scaling_max_freq is ignored - alternative shell script

[Leon Meier]

One can also sidestep writing to /tmp in the script in 
/lib/systemd/system-sleep/:


#!/bin/bash
### Ensure that the frequency is restored upon resuming from suspend
# The array to store frequencies:
declare -a frequencies
# Number of processors minus 1:
N=$((`nproc --all`-1))
case "${1}" in
  post)
# Read the old values:
for i in `seq 0 $N`; do frequencies[$i]=`cat 
/sys/devices/system/cpu/cpu$i/cpufreq/scaling_max_freq`; done

# Write a junk value first:
for i in `seq 0 $N`; do echo 1${frequencies[$i]} > 
/sys/devices/system/cpu/cpu$i/cpufreq/scaling_max_freq; done

# Let the file kernel digest the previous requests a bit:
sleep 1
# Write the old values:
for i in `seq 0 $N`; do echo ${frequencies[$i]} > 
/sys/devices/system/cpu/cpu$i/cpufreq/scaling_max_freq; done

;;
esac

Though this script now avoids writing into /tmp, it's a terribly wild 
hack again invoking bash and other utilities. I'm feeling that it is too 
much an overkill as opposed to doing the right thing in the kernel.

Bug#880203: closed by Ben Hutchings <b...@decadent.org.uk> (Re: Fwd: Re: Bug#880203: After suspend, cpufreq/scaling_max_freq is ignored)

[Leon Meier]

On 01.11.2017 13:38, Ben Hutchings wrote:

On Tue, 31 Oct 2017 13:25:11 +0100 Leon Meier <leon.me...@yandex.ru> wrote:

On 31.10.2017 11:39, Debian Bug Tracking System wrote:

Yes, but that doesn't mean we can do anything about it.


Why not simply re-issue the request setting the performance-level after
resume?


The driver does that.



Oh. But in this case the effect of this action is not visible on my machine.

Bug#880203: After suspend, cpufreq/scaling_max_freq is ignored - (wild hack) shell script

[Leon Meier]

On 31.10.2017 13:25, Leon Meier wrote:

On 31.10.2017 11:39, Debian Bug Tracking System wrote:

Yes, but that doesn't mean we can do anything about it.


Why not simply re-issue the request setting the performance-level after 
resume?


You could at least suggest a script similar to the following one to be 
added to /lib/systemd/system-sleep.


#!/bin/sh
### Ensure that the frequency is stored/restored upon resume
case "${1}" in
  pre)
# Store the old frequency
for i in `seq 0 7`; do cat 
/sys/devices/system/cpu/cpu$i/cpufreq/scaling_max_freq > 
/tmp/scaling_max_freq$i; done

;;
  post)
# Wild hack: insert a junk value first
for i in `seq 0 7`; do echo 999 > 
/sys/devices/system/cpu/cpu$i/cpufreq/scaling_max_freq; done

# Set the old frequency
for i in `seq 0 7`; do
  cat /tmp/scaling_max_freq$i > 
/sys/devices/system/cpu/cpu$i/cpufreq/scaling_max_freq

  rm -f /tmp/scaling_max_freq$i;
done
;;
esac

Exercise for the reader: automatically determine the number of CPUs, 
ensure that created files have fresh names, that there is sufficient 
unused space in /tmp, and that proper error handling is done if it is 
not the case.


However, really, this is much better done in the kernel manipulating 
p-states directly rather than through the overkill of wild hacks and 
invoking a shell script modifying various places in the file system.

Bug#880203: closed by Ben Hutchings <b...@decadent.org.uk> (Re: Fwd: Re: Bug#880203: After suspend, cpufreq/scaling_max_freq is ignored)

[Leon Meier]

On 31.10.2017 11:39, Debian Bug Tracking System wrote:

Yes, but that doesn't mean we can do anything about it.


Why not simply re-issue the request setting the performance-level after 
resume?

Bug#880203: After suspend, cpufreq/scaling_max_freq is ignored

[Leon Meier]

tags 880203 - moreinfo
thanks


Ben, thank you for the clarification.

On 31.10.2017 00:35, Ben Hutchings wrote:

Control: tag -1 moreinfo

If this system has an Intel CPU, I'm afraid this is expected behaviour.
  They no longer allow the OS to set an exact frequency, only a 'P-
state' (performance level).  The Linux cpufreq driver for these
processors (intel_pstate) translates the requested frequency into a P-
state, but the actual frequency is controlled by an embedded controller
that may choose a higher or lower value.


However, the cpufreq driver is not loaded in my case:

# lsmod | grep cpufreq
# lsmod | grep intel_pstate
#

Would loading some driver help?

Your text explains _what_ is happening, but not why the embedded 
controller chooses a higher frequency only upon suspend and not 
earlier, when the root actually sets scaling_max_freq or when the 
machine is loaded with heavy applications (firefox + thunderbird + video 
player + some mathematical computation in the background + word 
processor + ...)


The way I understand it is that when the root writes to the file 
scaling_max_freq, a performance-level--setting request, let's call it R, 
goes to the embedded controller, which then chooses some frequency. 
Probably, upon suspend/resume, the controller thinks that there is more 
job to do (and, in general, there are some running applications before 
suspend which do incur work), and raises the actual frequency. Now, 
after suspend, the kernel _could_, in addition to what it usually 
does, re-issue the request R to "undo" the too eager action of the 
embedded controller. If a user herself writes the same value 120 to 
scaling_max_freq again, nothing happens.


The current behavior might be expected from the viewpoint of the 
processor and of the embedded controller; I don't wish to question that. 
But, from the viewpoint of the user, this is extremely, overly 
_counterintuitive_. The user simply expects that the machine behaves the 
same after closing the laptop lid. E.g., that if the user 
enjoyed noise-free Skype calls or noise-free music before, she expects 
noise-free Skype calls and noise-free music afterwards. The noise, in 
turn, depends on the fan, which depends on the produced heat, which 
depends on the frequency...



Unless you can show that a different kernel version reproducibly shows
different results, or you're not using an Intel CPU, I don't think
there's anything to be done here.

It's Intel. Unfortunately, I don't have another Linux kernel to test on 
the same machine right now.



Ben.



Here is the processor data (before suspend):

$ cat /proc/cpuinfo | head -27
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 58
model name  : Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz
stepping: 9
microcode   : 0x1c
cpu MHz : 1200.024
cache size  : 6144 KB
physical id : 0
siblings: 8
core id : 0
cpu cores   : 4
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe 
syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl 
xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor 
ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic 
popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm epb 
tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm 
ida arat pln pts

bugs:
bogomips: 5183.16
clflush size: 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

After s, the MHz value goes up to some value, up to 2600.

Best regards,
Leon

Bug#880203: After suspend, cpufreq/scaling_max_freq is ignored

[Leon Meier]

Package: linux-image-4.9.0-4-amd64
Version: 4.9.51-1

To avoid fan noise, I set up my laptop such that it sets a low CPU 
frequency upon boot via


for i in `seq 0 7`; do echo 120 > 
/sys/devices/system/cpu/cpu$i/cpufreq/scaling_max_freq; done


in a startup script.

This all goes well until I make a break in my work by closing the laptop 
lid (which then suspends the laptop) and resuming later. After resume, 
we still have low frequency in scaling_max_freq, but this setting is 
ignored:


$ for i in `seq 0 7`; do cat 
/sys/devices/system/cpu/cpu$i/cpufreq/scaling_max_freq; done

120
120
120
120
120
120
120
120
$ cat /proc/cpuinfo | grep MHz
cpu MHz : 1899.853
cpu MHz : 1900.964
cpu MHz : 1899.853
cpu MHz : 1899.853
cpu MHz : 1899.853
cpu MHz : 1899.853
cpu MHz : 1899.853
cpu MHz : 947.546
$ for i in `seq 0 7`; do cat 
/sys/devices/system/cpu/cpu$i/cpufreq/scaling_governor; done

powersave
powersave
powersave
powersave
powersave
powersave
powersave
powersave

Moreover, the fan kicks in, and the laptop feels to run without speed 
restrictions (noisy fan, etc.)


Any bugfix?

Thanks in advance,
Leon

Bug#879467: Remove Debian package mathpartir from Debian repositories or update it

[Leon Meier]

thanks for your bug report, I was not aware of the fact that mathpartir
is now included in texlive-science. This is good news, I will replace
the package by a transational package to teclive-science, then.

-Ralf.


Ok, Ralf, thanks!

Bug#879467: Remove Debian package mathpartir from Debian repositories or update it

[Leon Meier]

Package: mathpartir
Version: 1.2.0-6

As of today, the file mathpartir.sty from this Debian package has 
version 1.2.0 from 2005/12/20. On my system, the file goes to

/usr/share/texmf/tex/latex/mathpartir/mathpartir.sty

The Debian package texlive-science contains a newer mathpartir.sty, 
version 1.3.2 from 2016/02/24. On my system, the file goes to

/usr/share/texlive/texmf-dist/tex/latex/mathpartir/mathpartir.sty

Probably, the Debian package mathpartir should go away from the 
repositories or at least be updated. Offering the same LaTeX package 
mathpartir.sty with two different versions doesn't make too much sense.


Best regards,
Leon

Bug#821269: (no subject)

[Leon Meier]

found 821269 52.4.0esr-1~deb9u1
thanks

Right. Under the assumption that myspell is replaced by hunspell, the 
same change should occur in firefox. As of today, it is still not the case.


Leon

Bug#877424: closed by Brian Potkin <claremont...@gmail.com> (Re: Bug#877424: Cleanup iPhone manual and prepare for stretch)

[Leon Meier]

Moreover, I really think that Debian OS will profit from the
interoperability with iPhone immensely.


Do you have any ideas on how we might profit from that?

It could be a business decision, so, I will send a non-public e-mail.


I will check with competitors, of course ;-)


The Arch wiki is the usual place people check for documentation:

https://wiki.archlinux.org/index.php/iOS
https://wiki.archlinux.org/index.php/IPhone_Tethering


Thanks!

Bug#877424: closed by Brian Potkin <claremont...@gmail.com> (Re: Bug#877424: Cleanup iPhone manual and prepare for stretch)

[Leon Meier]

if Debian is interested in hiring me.


I'm sorry, but Debian is a non-profit project maintained by
volunteers. We would definitely welcome your help maintaining the wiki
when you have time though.

This will not happen: I have to have my lunch before I can finance yours 
;-).  Moreover, I really think that Debian OS will profit from the 
interoperability with iPhone immensely. I will check with competitors, 
of course ;-).

Bug#877424: closed by Brian Potkin <claremont...@gmail.com> (Re: Bug#877424: Cleanup iPhone manual and prepare for stretch)

[Leon Meier]

reopen 877424
thanks

Dear Brian:

I'm not aware of any of the involved interfaces.  Therefore, if I were 
to make stretch working with iPhone with iOS 11, I'd assume that I'd 
need documentation on the interfaces (which might be proprietary in case 
of iOS 11) and about one full-time week.  I'm on the job market from 
December 2017 if Debian is interested in hiring me.


Best,
Leon



On 10/02/2017 11:36 AM, Debian Bug Tracking System wrote:

This is an automatic notification regarding your Bug report
which was filed against the wiki.debian.org package:

#877424: Cleanup iPhone manual and prepare for stretch

It has been closed by Brian Potkin .

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Brian Potkin 
 by
replying to this email.

Bug#877424: Cleanup iPhone manual and prepare for stretch

[Leon Meier]

Package: wiki.debian.org

Please update https://wiki.debian.org/iPhone .

As of today, this manual has nothing to offer for Debian stretch 9.1 and 
iOS 11.0.1. The various solutions for older combinations fail for me. 
Even worse, this manual seems to be in a raw, cluttered state even for 
older Debian versions. Please test and update with at least one working 
scenario for this combination.


Ideally, this manual should let the user choose his/her Debian version, 
his/her iOS version, and direct him/her to the corresponding howto.


Thanks in advance,
Leon

Bug#869618: bib2ris ignores year

[Leon Meier]

What OS do you run?

$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 9.1 (stretch)
Release:9.1
Codename:   stretch

$ uname -a
Linux amhost 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u2 (2017-06-26) 
x86_64 GNU/Linux


$ locale
LANG=de_DE.utf8
LANGUAGE=
LC_CTYPE="de_DE.utf8"
LC_NUMERIC="de_DE.utf8"
LC_TIME="de_DE.utf8"
LC_COLLATE="de_DE.utf8"
LC_MONETARY="de_DE.utf8"
LC_MESSAGES="de_DE.utf8"
LC_PAPER="de_DE.utf8"
LC_NAME="de_DE.utf8"
LC_ADDRESS="de_DE.utf8"
LC_TELEPHONE="de_DE.utf8"
LC_MEASUREMENT="de_DE.utf8"
LC_IDENTIFICATION="de_DE.utf8"
LC_ALL=


Ports/packages or compiled from sources?

Packages. Let's have a look:

$ which bib2ris
/usr/bin/bib2ris

$ dpkg -S /usr/bin/bib2ris
refdb-clients: /usr/bin/bib2ris

$ aptitude show refdb-clients | head -4
Paket: refdb-clients
Version: 1.0.2-3
Neu: ja
Zustand: Installiert



What version of the btparse library?

$ aptitude show libbtparse1 | head -4
Paket: libbtparse1
Version: 0.78-1
Zustand: Installiert
Automatisch installiert: ja


Do you have any entries in your global or personal bib2risrc files?
If any configuration files exist at all, I did not touch them. I did a 
pretty much clean installation of refdb-clients, so they are in the 
state left by the installer.

Bug#869618: bib2ris ignores year

[Leon Meier]

Package: refdb-clients
Version: 1.0.2-3

The year field in the .bib files is ignored. Example input file 
mybiblio.bib:


@article{entry,
  author= {John Smith},
  title = {Awesome Title},
  journal = {JACM},
  year  = {2006},
  pages = {1--2}
}

Running `bib2ris mybiblio.bib` results in

TY  - JOUR
ID  - entry
AU  - Smith,John
JF  - JACM
SP  - 1
EP  - 2
PY  - ///
TI  - Awesome Title
ER  -

As you see, the year is missing in the output. Trying various 
command-line options did not help. Any improvement would be greatly 
appreciated.


Thanks in advance!
Leon

Bug#865396: xelatex + unicode-math + \big = ↯

[Leon Meier]

That doesn't look possible. Updates to stable are very rare, and in this
case we would need to push a rather uncomfortably large set of changes.

If there is a simple and confined patch to fix this, that would be fine,
but I don't see it.


Hi Norbert,

thank you for letting me know. That's unfortunate, although the 
difference in the last digit of the XeTeX version seems minor to me.


I guess, in this case feel free to view it as a bug report against the 
xetex version in testing... (I did not try to install the version from 
unstable/experimental so far, but if it is brand new, the bug is likely 
to be fixed there.)


Best,
Leon

Bug#865396: xelatex + unicode-math + \big = ↯

[Leon Meier]

Package: texlive-xetex
Version: 2016.20170123-5
Severity: minor

Details:
http://tex.stackexchange.com/questions/375355/xelatex-unicode-math-big

In short, the output of xelatex on

\documentclass{article}
\usepackage{unicode-math}
\begin{document}
\(\bigl[
,
  \mathchoice%
  {}%
  {}%
  {}%
  {\hbox{$\scriptscriptstyle a$}}
\bigr]\)
\end{document}

is buggy.

XeTeX Version 3.14159265-2.6-0.6 has the bug, and 
3.14159265-2.6-0.8 doesn't. Could you suggest the newer version into 
stable?

Bug#783741: (no subject)

[Leon Meier]

found 783741 live-image-gnome-desktop/5.0~a5-2
severity 783741 important
thanks

When putting debian-live-8.7.1-amd64-gnome-desktop.iso on a USB stick 
and booting the USB stick in a Legacy mode, we still see a memtest86+ 
menu entry, but choosing this entry and pressing [Enter] leads nowhere.


Please repair - many thanks in advance!

Raising severity, since memory testing is considered to be one of the 
major functions of the live images.

Bug#858824: closed by Ben Hutchings <b...@decadent.org.uk> (Re: Bug#858824: Disrupting messages to tty)

[Leon Meier]

> This is not a bug.  Use a support channel to ask questions about
> managing console output:
> https://www.debian.org/support

Thanks, Ben.  Do you mean an IRC channel?

Btw., I searched the documentation there. If the answer is there, it is 
not easy to find. That site seems (partially) unmaintained.


Other options listed there regarding asking don't work:

- The site ask.debian.net did not list my posted question.
- The site www.debianhelp.org says it's under maintenance.
- forums.debian.net rejects to register me using my e-mail address.

Bug#858824: Disrupting messages to tty

[Leon Meier]

Package: firmware-iwlwifi
Version: 20161130-2

When I'm doing whatever tasks in tty..., following messages get printed 
to the screen every couple of minutes:


iwlwifi ... L1 Enabled - LTR Disabled

along with a bunch of other, mostly iwlwifi-related messages.

They disrupt my workflow, overwriting the current screen contents. This 
is annoying. Are these messages important? Could these messages better 
go somewhere else?


Thanks is advance
Leon
[ 1917.007948] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[ 1917.014919] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[ 1917.015108] iwlwifi :03:00.0: Radio type=0x0-0x3-0x1
[ 1917.244098] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[ 1917.251786] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[ 1917.251981] iwlwifi :03:00.0: Radio type=0x0-0x3-0x1
[ 1917.349565] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 2233.012506] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[ 2233.032397] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[ 2233.032593] iwlwifi :03:00.0: Radio type=0x0-0x3-0x1
[ 2233.273367] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[ 2233.280979] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[ 2233.281169] iwlwifi :03:00.0: Radio type=0x0-0x3-0x1
[ 2233.394848] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 2280.802538] perf: interrupt took too long (3934 > 3917), lowering 
kernel.perf_event_max_sample_rate to 50750
[ 2549.008539] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[ 2549.015471] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[ 2549.015660] iwlwifi :03:00.0: Radio type=0x0-0x3-0x1
[ 2549.251304] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[ 2549.258240] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[ 2549.258433] iwlwifi :03:00.0: Radio type=0x0-0x3-0x1
[ 2549.354601] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 2864.995743] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[ 2865.002684] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[ 2865.002879] iwlwifi :03:00.0: Radio type=0x0-0x3-0x1
[ 2865.270886] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[ 2865.277820] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[ 2865.278009] iwlwifi :03:00.0: Radio type=0x0-0x3-0x1
[ 2865.381159] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3180.998535] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[ 3181.005556] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[ 3181.005743] iwlwifi :03:00.0: Radio type=0x0-0x3-0x1
[ 3181.237671] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[ 3181.244599] iwlwifi :03:00.0: L1 Enabled - LTR Disabled
[ 3181.244788] iwlwifi :03:00.0: Radio type=0x0-0x3-0x1
[ 3181.343180] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3358.835933] perf: interrupt took too long (4932 > 4917), lowering 
kernel.perf_event_max_sample_rate to 40500

Bug#856993: closed by Norbert Preining <prein...@debian.org> (Bug#856993: fixed in texlive-lang 2016.20170123-5)

[Leon Meier]

Thank you, Norbert! Let's hope everything goes well.

Bug#856993: Warnings "Add \usepackage{fontspec} to the (frenchb.ldf) preamble of your document"

[Leon Meier]

Dear Norbert:

I see. I'm not that good to vouch for or against the correctness of the 
bugfix (if you are speaking about 
http://tex.stackexchange.com/questions/351377/french-add-usepackagefontspec-to-the-preamble-of-your-document) 
*alone*, but I trust you knowing latex better than me.


Thank you a lot in any case, I really appreciate that!

Leon

Bug#856993: Warnings "Add \usepackage{fontspec} to the (frenchb.ldf) preamble of your document"

[Leon Meier]

Package: texlive-lang-french
Version: 2016.20170123-3
Severity: important

Consider the input

\documentclass{article}
\usepackage{fontspec}
\usepackage[french,main=american]{babel}
% \usepackage{fontspec}%%% Doesn't matter where you use fontspec
\begin{document}
Nothing.
\end{document}

No matter which of the two lines including the fontspec package is 
enabled, the warning


Package frenchb.ldf Warning: Add \usepackage{fontspec} to the
(frenchb.ldf)preamble of your document, on input line 5.

is printed to the log when compiling with xelatex or lualatex.
The output file is ok.


The bug is apparently repaired upstream in babel-french version 3.2g. 
Please push it to testing before it gets stable.


Justification of severity: we rely on warnings to check that our 
documents are well-built. Having one more warning is a big red sign that 
something might have gone wrong during compilation, and we would not 
like to have this distraction months and years long in stable.


Thanks in advance,

Leon

Bug#839069: (no subject)

[Leon Meier]

affects 839069 util-linux
quit

# since fstrim is in util-linux

Bug#839069: fstrim doesn't work on ntfs

[Leon Meier]

Package: ntfs-3g
Version: 1:2016.2.22AR.1-3

My setup is as follows:

# cat /etc/fstab | grep -i ntfs
/dev/sda2   /media/my_data  ntfs-3g 
rw,user,noatime,discard,commit=300  0   0

# aptitude show util-linux | grep Version
Version: 2.28.1-1
# aptitude show ntfs-3g | grep Version
Version: 1:2016.2.22AR.1-3
# uname -a
Linux my_host_name 4.6.0-1-amd64 #1 SMP Debian 4.6.4-1 (2016-07-18) 
x86_64 GNU/Linux

# dmesg| grep "ATA.*SSD"
[2.111271] ata1.00: ATA-8: SAMSUNG SSD PM830 2.5" 7mm 512GB, 
CXM03D1Q, max UDMA/133
[2.124231] scsi 0:0:0:0: Direct-Access ATA  SAMSUNG SSD PM83 
3D1Q PQ: 0 ANSI: 5


Now:
# mount /media/my_data/
# ls /media/my_data/
my_private_directory $RECYCLE.BIN  System Volume Information 
Windows10Upgrade

# fstrim -v /media/my_data
/media/my_data/: 104,2 GiB (111868387328 bytes) trimmed
# fstrim -v /media/my_data
/media/my_data/: 104,2 GiB (111868387328 bytes) trimmed


Given that the current version of the ntfs-3g driver supports trimming, 
and given that fstrim ran twice, I expect that the second command 
reports "0 B (0 bytes) trimmed", contrary to the above.


Changing ntfs-3g to ntfs in /etc/fstab has no influence.

Bug#837072: GtkScrollbar and EmacsFixed are "drawn without a current allocation"

[Leon Meier]

Also occurs for me for emacs24 version 24.5+1-7.
Emacs clutters the xterm from where it is launched completely, which 
renders xterm half-useless:


...

(emacs:12626): Gtk-WARNING **: GtkScrollbar 0x312c900 is drawn without a 
current allocation. This should not happen.


(emacs:12626): Gtk-WARNING **: EmacsFixed 0xd51130 is drawn without a 
current allocation. This should not happen.


...

I'm voting for raising the severity, since the bug affects several 
people and the usability of another application (xterm).

Bug#838002: Libreoffice-writer formatting dialogs take too long to open

[Leon Meier]

tag 838002 - moreinfo
thanks

On 16.09.2016 12:13, Rene Engelhard wrote:

tag 838002 + moreinfo
thanks

Hi,

On Fri, Sep 16, 2016 at 11:37:04AM +0200, Leon Meier wrote:

Opening the dialog Format->Character from the menu took around 1 min 41 sec.
I tried:
- removing the .config/libreoffice directory
- increasing usable memory in the extras->options
- # fc-cache -f -v
After the last action, the delay went down to 1 minute. Still way to long.
The bug is consistently repeatable.
My distribution is an up-to-date sid.


Then you probably got affected by #837356, too?


Yes.


Any help?


Yes, see above. (And this is per se not "something for help" but a bug tracking
system ;))

Thank you.
Downgrading libgtk-3 from to libgtk-3-0_3.20.9-1 fixes the bug.
Please feel free to merge.



Regards,

Rene

Bug#838002: Libreoffice-writer formatting dialogs take too long to open

[Leon Meier]

Package: libreoffice-writer
Version: 1:5.2.1-1

Opening the dialog Format->Character from the menu took around 1 min 41 
sec. I tried:

- removing the .config/libreoffice directory
- increasing usable memory in the extras->options
- # fc-cache -f -v
After the last action, the delay went down to 1 minute. Still way to long.
The bug is consistently repeatable.
My distribution is an up-to-date sid.

Any help?

Bug#827195: evince plugin won't open postscript

[Leon Meier]

found browser-plugin-evince/3.21.4-1
thanks

The used version of firefox-esr is 45.3.0esr-1~deb8u1

A file which cannot be opened is, e.g.,
http://www.math.chalmers.se/~palbin/rickard.ps

The browser hangs for a few minutes, then the blank tab is displayed.

In fact, no postscript file can be opened from the browser.

Bug#832077: Info received (emacs clutter screen on windows switch)

[Leon Meier]

By the way, I don't know who is the culprit: libgtk-3-0, emacs, or 
someone else. So please consider my found / nofound tags just as 
additional information on my configuration rather as a bug source hint. 
Sorry about that.

Bug#832077: emacs clutter screen on windows switch

[Leon Meier]

found 832077 libgtk-3-0/3.21.5-3
thanks

Bug#832077: emacs clutter screen on windows switch

[Leon Meier]

found 832077 emacs/46.1
thanks

The message

(emacs:6144): Gtk-WARNING **: GtkWindow 0xc50270 is drawn without a 
current allocation. This should not happen.


is printed to xterm from where emacs was started. Printing happens  when 
the emacs window gets the focus due to a left-button mouse click.


For me, it's not a huge trouble, but still, annoying.

Bug#833532: icedove crashes sometimes. To crash reproducibly, install calendar-google-provider

[Leon Meier]

On 12.08.2016 08:56, Carsten Schoenert wrote:

notfound 833532 calendar-google-provider/1:45.2.0-2
notfound 833532 iceowl-extension/1:45.2.0-2+b1
thanks

The error is in the icedove package, not in any other related package
from the source package.

Hello Leon,

On Fri, Aug 12, 2016 at 12:25:06AM +0200, Leon Meier wrote:

If icedove is started with calendar-google-provider (version 1:45.2.0-2), it
always crashes during the start.


this completely depends on your local machine and how the kernel is
organizing the RAM. I haven't seen a crash with this version for several
days.


If I disable the add-on or remove the package
calendar-google-provider, icedove starts sometimes as usual, and
sometimes crashes. It seems to me that without
calendar-google-provider, the crash happens exactly every second time
(but it might be a coincidence).


That's simply coincidence.


In safe mode, no crash is observed. Feel free to reassign
appropriately to another package if deemed necessary.


As icedove isn't crashing that much in safe mode isn't surprising at
all as this is the intentation behind the safe mode.


Justification for severity: calendar-google-provider is pulled in by default
as a recommended package, making the default setup unusable.


That's not true. calendar-google-provider is only a Suggest (not a
Recommends) from iceowl-extension. It wont installed automatically in
any time.
As of this very moment, indeed, you are right, calendar-google-provider 
is indeed only suggested; I take the above sentence partially back. 
However, I do not remember having ever installed it manually, so it most 
probably have been recommended (or required) in the past, or it got 
automatically installed in some other way.





$ apt show iceowl-extension
Package: iceowl-extension
Version: 1:45.2.0-2+b1
...
Provides: calendar-timezones
Depends: icedove (>= 1:45.2.0-2+b1), libc6 (>= 2.7), libgcc1 (>= 1:3.0), libnspr4 (>= 
2:4.9-2~) | libnspr4-0d (>= 1.8.0.10), libstdc++6 (>= 4.1.1)
Suggests: calendar-google-provider, fonts-lyx



[...]

There are a few weird messages printed to the console anyway even without
calendar-google-provider. These messages may or may not be related:

my_user_name@my_host:~$ icedove &
[1] 6236


It isn't usful to push the running binary into background while trying
to debug the binary itself. You wont see all the messages than.

[...]

my_user_name@my_host:~$ [calBackendLoader] Using libical backend at 
/usr/lib/icedove/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/components/libical-manifest

...

A coding exception was thrown in a Promise rejection callback.
See 
https://developer.mozilla.org/Mozilla/JavaScript_code_modules/Promise.jsm/Promise

Full message: TypeError: Cu is null
Full stack: 
exports.FilterStorage.loadFromDisk/readFile 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/bootstrap.js
-> 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/lib/filterStorage.js:380:11
exports.IO.readFromFile/onError@resource://gre/modules/addons/XPIProvider.jsm
-> 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/bootstrap.js
-> 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/lib/io.js:149:9
Handler.prototype.process@resource://gre/modules/Promise.jsm ->
resource://gre/modules/Promise-backend.js:936:21
this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm ->
resource://gre/modules/Promise-backend.js:812:7
this.PromiseWalker.scheduleWalkerLoop/<@resource://gre/modules/Promise.jsm
-> resource://gre/modules/Promise-backend.js:746:1

*


All the messages here are from the xul-ext-adblock-plus package and not
relevant to the icedove bug.

Regards
carsten

Carsten, your comments are probably very helpful for the programmers; 
thanks again!


Best,

Leon

Bug#833532: icedove crashes sometimes. To crash reproducibly, install calendar-google-provider

[Leon Meier]

found 833532 icedove/1:45.2.0-2+b1
found 833532 calendar-google-provider/1:45.2.0-2
found 833532 iceowl-extension/1:45.2.0-2+b1
severity 833532 grave
thanks
--

If icedove is started with calendar-google-provider (version 
1:45.2.0-2), it always crashes during the start. If I disable the add-on 
or remove the package calendar-google-provider, icedove starts sometimes 
as usual, and sometimes crashes. It seems to me that without 
calendar-google-provider, the crash happens exactly every second time 
(but it might be a coincidence). In safe mode, no crash is observed. 
Feel free to reassign appropriately to another package if deemed necessary.


Justification for severity: calendar-google-provider is pulled in by 
default as a recommended package, making the default setup unusable.


There are a few weird messages printed to the console anyway even 
without calendar-google-provider. These messages may or may not be related:




my_user_name@my_host:~$ icedove &
[1] 6236
my_user_name@my_host:~$ [calBackendLoader] Using libical backend at 
/usr/lib/icedove/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/components/libical-manifest


[1]+  Speicherzugriffsfehler  icedove
my_user_name@my_host:~$
my_user_name@my_host:~$
my_user_name@my_host:~$ icedove &
[1] 6309
my_user_name@my_host:~$ [calBackendLoader] Using libical backend at 
/usr/lib/icedove/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/components/libical-manifest

*** BUG ***
In pixman_region32_reset: Malformed region region
Set a breakpoint on '_pixman_log_error' to debug

*
A coding exception was thrown and uncaught in a Task.

Full message: TypeError: require is not a function
Full stack: 
exports.Utils.yield@resource://gre/modules/addons/XPIProvider.jsm -> 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/bootstrap.js 
-> 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/lib/utils.js:354:19
INIParser.prototype.process@resource://gre/modules/addons/XPIProvider.jsm 
-> 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/bootstrap.js 
-> 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/lib/filterStorage.js:798:7
exports.IO.readFromFile/onProgress@resource://gre/modules/addons/XPIProvider.jsm 
-> 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/bootstrap.js 
-> 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/lib/io.js:97:15
exports.IO.readFromFile/<@resource://gre/modules/addons/XPIProvider.jsm 
-> 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/bootstrap.js 
-> 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/lib/io.js:182:11

TaskImpl_run@resource://gre/modules/Task.jsm:315:40
Handler.prototype.process@resource://gre/modules/Promise.jsm -> 
resource://gre/modules/Promise-backend.js:933:23
this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm -> 
resource://gre/modules/Promise-backend.js:812:7
this.PromiseWalker.scheduleWalkerLoop/<@resource://gre/modules/Promise.jsm 
-> resource://gre/modules/Promise-backend.js:746:1


*
*
A coding exception was thrown in a Promise rejection callback.
See 
https://developer.mozilla.org/Mozilla/JavaScript_code_modules/Promise.jsm/Promise


Full message: TypeError: Cu is null
Full stack: 
exports.FilterStorage.loadFromDisk/readFile-> 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/bootstrap.js 
-> 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/lib/filterStorage.js:380:11
exports.IO.readFromFile/onError@resource://gre/modules/addons/XPIProvider.jsm 
-> 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/bootstrap.js 
-> 
file:///usr/share/mozilla/extensions/%7B3550f703-e582-4d05-9a08-453d09bdfdc6%7D/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D/lib/io.js:149:9
Handler.prototype.process@resource://gre/modules/Promise.jsm -> 
resource://gre/modules/Promise-backend.js:936:21
this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm -> 
resource://gre/modules/Promise-backend.js:812:7
this.PromiseWalker.scheduleWalkerLoop/<@resource://gre/modules/Promise.jsm 
-> resource://gre/modules/Promise-backend.js:746:1


*

[1]+  Fertig  icedove
my_user_name@my_host:~$


Thanks in advance for 

Bug#702082: evince doesn't handle double-struck capital K (핂) in the bookmarks

[Leon Meier]

severity 702082 normal
found 702082 3.20.1-1
thanks

I believe that the file in the attachment is another manifestation of 
the same bug: we wish to have A핂B displayed in the table of contents, 
but we don't get it. The message


(evince:12408): Gtk-WARNING **: Failed to set text from markup due to 
error parsing markup: Error on line 1 char 17: Invalid UTF-8 encoded 
text in name - not valid 'A\xed\xa0\xb5\xed\xb5\x82B'


is printed to the xterm from which evince was started.

(
An aside for the curious: the file was generated by running pdflatex on

\documentclass{article}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{amsfonts}
\usepackage[unicode]{hyperref}
\begin{document}
\section{A\texorpdfstring{\(\mathbb{K}\)}{핂}B}
\end{document}
)

Thank you in advance for repairing!

Best, Leon



qq.pdf
Description: Adobe PDF document

Bug#456943: (no subject)

[Leon Meier]

As of today, the test case

echo " 
1234" | grep --color=auto '[1-9]'

 (80 spaces and 1234)

still fails in (u)xterm. Any resolution in sight?

(Sorry for not providing any opinion of _how_ to resolve it technically 
at the moment; I'm not good enough for that. It is just the bug has been 
kind of disturbing me for a few years already...)

Bug#829330: Please update hyperref from version v6.83p to v6.83q

[Leon Meier]

Please update hyperref from version v6.83p to v6.83q.


Will be in the next checkout from upstream TeX Live which
already contains the q version.


Thanks for the reply and thanks in advance for taking care of it! Sorry 
for the impatience; I will be awaiting the next checkout with delight.

Bug#829330: Please update hyperref from version v6.83p to v6.83q

[Leon Meier]

Package: texlive-latex-base
Version: 2016.20160623-1

Please update hyperref from version v6.83p to v6.83q.
The bug

http://tex.stackexchange.com/questions/315462/texlive-2016-hyperref-cleverref-incompatibility

is extremely uncomfortable: valid documents don't compile, making the 
package half-useless for me at this very point of time. The bug is fixed 
on CTAN, so you just need to repackage.


Thanks in advance

Leon