Bug#1036899: logiops: logid does not work for MX Master 3

[Hendrik Tews]

Hi,

On 2023-06-05 10:22:35, Chow Loong Jin  wrote:

> Could you check if 0.3.1-1 (in unstable) or 0.3.2-1 (in experimental) is
> working for you?

thanks for following up. Both 0.3.1-2 from unstable and 0.3.2-1 from
experimental work. (Unexpected to me, because I reproduced the problem
with the newest upstream version.)

Version 0.3.1-1 is the version from testing, this version does not
work.

Hendrik

Bug#1036899: logiops: logid does not work for MX Master 3

[Hendrik Tews]

Package: logiops
Version: 0.3.1-1
Severity: important
X-Debbugs-Cc: none, Hendrik Tews 

Dear Maintainer,

after upgrading to logiops version 0.3.1-1 the logid daemon does not
seem to do anything any more. For my configuration the symptom is that
the thumb button is no longer mapped to button 2. The problem seems to
be also present in the current upstream version (v0.3.2), see upstream
issue 387 (https://github.com/PixlOne/logiops/issues/387).

For now I downgraded to 0.2.3-1+b1, which is still working fine.

Best regards,

Hendrik


-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages logiops depends on:
ii  libc6   2.36-9
ii  libconfig++9v5  1.5-0.4
ii  libevdev2   1.13.0+dfsg-1
ii  libgcc-s1   12.2.0-14
ii  libglib2.0-02.74.6-2
ii  libstdc++6  12.2.0-14
ii  libudev1252.6-1

logiops recommends no packages.

logiops suggests no packages.

-- Configuration Files:
/etc/logid.cfg changed:
devices: ({
  name: "Wireless Mouse MX Master 3";
  # A lower threshold number makes the wheel switch to free-spin mode
  # quicker when scrolling fast.
  smartshift: {
on: false;
threshold: 3;
  };
  hiresscroll: {
hires: true;
invert: false;
target: false;
  };
  # Higher numbers make the mouse more sensitive (cursor moves faster),
  # 4000 max for MX Master 3.
  dpi: 1000;
  buttons: (
# Make thumb button 2.
{ cid: 0xc3;
  action = {
type: "Keypress";
keys: ["BTN_MIDDLE"];
  };
},
# top button
{ cid: 0xc4;
  action = {
type = "ToggleSmartshift";
  };
}
  );
});


-- no debconf information

Bug#1029273: linux-image-6.1.0-1-amd64: screen on usb-c dock works only once

[Hendrik Tews]

Package: src:linux
Version: 6.1.4-1
Severity: important
X-Debbugs-Cc: none, Hendrik Tews 

Dear Maintainer,

-- Package-specific info:
** Version:
Linux version 6.1.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-13) 12.2.0, GNU ld (GNU Binutils for Debian) 2.39.90.20221231) #1 SMP 
PREEMPT_DYNAMIC Debian 6.1.4-1 (2023-01-07)

** Command line:
BOOT_IMAGE=/vmlinuz-6.1.0-1-amd64 root=/dev/mapper/cert2--vg-root1 ro quiet

** Tainted: OE (12288)
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
[  134.076872] usb 7-1.1: Manufacturer: Realtek
[  134.076874] usb 7-1.1: SerialNumber: 30101
[  134.225874] usb 7-1.3: new SuperSpeed Plus Gen 2x1 USB device number 8 using 
xhci_hcd
[  134.250618] usb 7-1.3: New USB device found, idVendor=17ef, idProduct=a393, 
bcdDevice= d.23
[  134.250630] usb 7-1.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[  134.250634] usb 7-1.3: Product: USB3.1 Hub
[  134.250637] usb 7-1.3: Manufacturer: VIA Labs, Inc.
[  134.280923] hub 7-1.3:1.0: USB hub found
[  134.281211] hub 7-1.3:1.0: 4 ports detected
[  134.286267] [drm] DP Alt mode state on HPD: 1
[  134.344854] usb 7-1.1: reset SuperSpeed USB device number 7 using xhci_hcd
[  134.379153] r8152 7-1.1:1.0 (unnamed net_device) (uninitialized): Invalid 
header when reading pass-thru MAC addr
[  134.379247] r8152 7-1.1:1.0: firmware: direct-loading firmware 
rtl_nic/rtl8153b-2.fw
[  134.391120] [drm] DM_MST: starting TM on aconnector: 15f96e41 [id: 
94]
[  134.396619] r8152 7-1.1:1.0: load rtl8153b-2 v1 10/23/19 successfully
[  134.429215] r8152 7-1.1:1.0 eth0: v1.12.13
[  134.658821] [drm] Downstream port present 1, type 0
[  134.820305] usb 6-1.3.3: new high-speed USB device number 12 using xhci_hcd
[  134.884639] r8169 :02:00.0 enp2s0f0: Link is Down
[  134.987820] usb 6-1.3.3: New USB device found, idVendor=17ef, 
idProduct=a395, bcdDevice=60.90
[  134.987828] usb 6-1.3.3: New USB device strings: Mfr=10, Product=11, 
SerialNumber=0
[  134.987831] usb 6-1.3.3: Product: USB2.0 Hub
[  134.987834] usb 6-1.3.3: Manufacturer: Lenovo
[  135.048952] hub 6-1.3.3:1.0: USB hub found
[  135.049262] hub 6-1.3.3:1.0: 4 ports detected
[  135.063149] r8152 7-1.1:1.0 enxf4a80d209805: renamed from eth0
[  135.140301] r8169 :05:00.0 enp5s0: Link is Down
[  135.340541] usb 6-1.3.3.1: new full-speed USB device number 13 using xhci_hcd
[  135.468641] usb 6-1.3.3.1: New USB device found, idVendor=17ef, 
idProduct=a38f, bcdDevice= 0.00
[  135.468653] usb 6-1.3.3.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[  135.468657] usb 6-1.3.3.1: Product: 40AS
[  135.468659] usb 6-1.3.3.1: Manufacturer: Cypress Semiconductor
[  135.468662] usb 6-1.3.3.1: SerialNumber: 1S40ASZKW2Y1ZW
[  135.540345] hid-generic 0003:17EF:A38F.0006: hiddev1,hidraw3: USB HID v1.11 
Device [Cypress Semiconductor 40AS] on usb-:07:00.4-1.3.3.1/input1
[  135.620675] usb 6-1.3.3.2: new full-speed USB device number 14 using xhci_hcd
[  135.930244] usb 6-1.3.3.2: New USB device found, idVendor=17ef, 
idProduct=a396, bcdDevice= 0.14
[  135.930258] usb 6-1.3.3.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[  135.930262] usb 6-1.3.3.2: Product: ThinkPad USB-C Dock Gen2 USB Audio
[  135.930265] usb 6-1.3.3.2: Manufacturer: Lenovo
[  135.930268] usb 6-1.3.3.2: SerialNumber: 
[  136.146506] input: Lenovo ThinkPad USB-C Dock Gen2 USB Audio as 
/devices/pci:00/:00:08.1/:07:00.4/usb6/6-1/6-1.3/6-1.3.3/6-1.3.3.2/6-1.3.3.2:1.3/0003:17EF:A396.0007/input/input34
[  136.204901] hid-generic 0003:17EF:A396.0007: input,hidraw4: USB HID v1.11 
Device [Lenovo ThinkPad USB-C Dock Gen2 USB Audio] on 
usb-:07:00.4-1.3.3.2/input3
[  136.512476] usb 6-1.2: new high-speed USB device number 15 using xhci_hcd
[  136.664411] usb 6-1.2: New USB device found, idVendor=18d1, idProduct=4ee1, 
bcdDevice= 4.40
[  136.664423] usb 6-1.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[  136.664426] usb 6-1.2: Product: Pixel 3a
[  136.664429] usb 6-1.2: Manufacturer: Google
[  136.664431] usb 6-1.2: SerialNumber: 9B1AY1GLXS
[  137.339778] IPv6: ADDRCONF(NETDEV_CHANGE): enxf4a80d209805: link becomes 
ready
[  137.340023] r8152 7-1.1:1.0 enxf4a80d209805: carrier on
[  144.634720] audit: type=1400 audit(1674224479.785:57): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cups-browsed" 
name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=2465 comm="cups-browsed" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[  144.637641] audit: type=1400 audit(1674224479.785:58): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cups-browsed" 
name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=2465 comm="cups-browsed" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[  144.655736] audit: type=1400 audit(1674224

Bug#1010156: logiops: systemd incompatibility - mouse mapping does not work

[Hendrik Tews]

Package: logiops
Version: 0.2.2-2
Severity: normal
X-Debbugs-Cc: none, Hendrik Tews 

Dear Maintainer,

thanks a lot for packaging this driver!

Unfortunately, the packaged version is incompatible with the
version of systemd currently shipped in testing, see
https://github.com/PixlOne/logiops/commit/911e91eeebf72417d081e2b0f7e3d4c6db83c37b

For me, the symptom is that button remapping of my MX Master 3
mouse does not work, while the invert hiresscroll feature did
work.

The upstream version from github works fine for me.

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

Kernel: Linux 5.16.0-6-amd64 (SMP w/12 CPU threads; PREEMPT)
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 not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages logiops depends on:
ii  libc6   2.33-7
ii  libconfig++9v5  1.5-0.4
ii  libevdev2   1.12.1+dfsg-1
ii  libgcc-s1   12-20220319-1
ii  libstdc++6  12-20220319-1
ii  libudev1250.4-1

logiops recommends no packages.

logiops suggests no packages.

-- Configuration Files:
/etc/logid.cfg changed:
devices: ({
  name: "Wireless Mouse MX Master 3";
  # A lower threshold number makes the wheel switch to free-spin mode
  # quicker when scrolling fast.
  smartshift: {
on: false;
threshold: 3;
  };
  hiresscroll: {
hires: true;
invert: false;
target: false;
  };
  # Higher numbers make the mouse more sensitive (cursor moves faster),
  # 4000 max for MX Master 3.
  dpi: 1000;
  buttons: (
# Make thumb button 2.
{ cid: 0xc3;
  action = {
type: "Keypress";
keys: ["BTN_MIDDLE"];
  };
},
# top button
{ cid: 0xc4;
  action = {
type = "ToggleSmartshift";
  };
}
  );
});


-- no debconf information

Bye,

Hendrik

Bug#990782: inkscape: /usr/share/inkscape/fonts does not exist

[Hendrik Tews]

Mattia Rizzolo  writes:

> That said, I'll ask upstream what they think about toning down
> the lines at DEBUG level, so they don't show up by default.

Thanks,

Hendrik

Bug#990782: inkscape: /usr/share/inkscape/fonts does not exist

[Hendrik Tews]

Package: inkscape
Version: 1.0.2-4
Severity: normal
X-Debbugs-Cc: none, Hendrik Tews 

Dear Maintainer,

each time I start inkscape, it complains

   ** (org.inkscape.Inkscape:44746): WARNING **: 11:29:57.779: Fonts dir 
'/usr/share/inkscape/fonts' does not exist and will be ignored.

   ** (org.inkscape.Inkscape:44746): WARNING **: 11:29:57.779: Fonts dir 
'/home/tews/.config/inkscape/fonts' does not exist and will be ignored.

It is possible to get rid of these warnings by just creating
these directories. But if inkscape expects these directories, the
package or inkscape should create them, shouldn't they?

Thanks,

Hendrik


-- System Information:
Debian Release: 11.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages inkscape depends on:
ii  libatkmm-1.6-1v5   2.28.0-3
ii  libc6  2.31-12
ii  libcairo2  1.16.0-5
ii  libcairomm-1.0-1v5 1.12.2-4
ii  libcdr-0.1-1   0.1.6-2
ii  libdbus-glib-1-2   0.110-6
ii  libdouble-conversion3  3.1.5-6.1
ii  libfontconfig1 2.13.1-4.2
ii  libfreetype6   2.10.4+dfsg-1
ii  libgc1 1:8.0.4-3
ii  libgcc-s1  10.2.1-6
ii  libgdk-pixbuf-2.0-02.42.2+dfsg-1
ii  libgdl-3-5 3.34.0-1
ii  libglib2.0-0   2.66.8-1
ii  libglibmm-2.4-1v5  2.64.2-2
ii  libgomp1   10.2.1-6
ii  libgsl25   2.6+dfsg-2
ii  libgtk-3-0 3.24.24-4
ii  libgtkmm-3.0-1v5   3.24.2-2
ii  libgtkspell3-3-0   3.0.10-1
ii  libharfbuzz0b  2.7.4-1
ii  libjpeg62-turbo1:2.0.6-4
ii  liblcms2-2 2.12~rc1-2
ii  libmagick++-6.q16-88:6.9.11.60+dfsg-1.3
ii  libpango-1.0-0 1.46.2-3
ii  libpangocairo-1.0-01.46.2-3
ii  libpangoft2-1.0-0  1.46.2-3
ii  libpangomm-1.4-1v5 2.42.1-1
ii  libpng16-161.6.37-3
ii  libpoppler-glib8   20.09.0-3.1
ii  libpoppler102  20.09.0-3.1
ii  libpotrace01.16-2
ii  librevenge-0.0-0   0.0.4-6+b1
ii  librsvg2-common2.50.3+dfsg-1
ii  libsigc++-2.0-0v5  2.10.4-2
ii  libsoup2.4-1   2.72.0-2
ii  libstdc++6 10.2.1-6
ii  libvisio-0.1-1 0.1.7-1+b1
ii  libwpg-0.3-3   0.3.3-1
ii  libx11-6   2:1.7.1-1
ii  libxml22.9.10+dfsg-6.7
ii  libxslt1.1 1.1.34-4
ii  python33.9.2-3
ii  zlib1g 1:1.2.11.dfsg-2

Versions of packages inkscape recommends:
ii  aspell   0.60.8-2
ii  fig2dev  1:3.2.8-3+b1
ii  imagemagick  8:6.9.11.60+dfsg-1.3
ii  imagemagick-6.q16 [imagemagick]  8:6.9.11.60+dfsg-1.3
ii  libimage-magick-perl 8:6.9.11.60+dfsg-1.3
ii  libwmf-bin   0.2.8.4-17
ii  python3-lxml 4.6.3-1
ii  python3-numpy1:1.19.5-1
ii  python3-scour0.38.2-1

Versions of packages inkscape suggests:
pn  dia   
pn  inkscape-tutorials
pn  libsvg-perl   
pn  libxml-xql-perl   
pn  pstoedit  
pn  python3-uniconvertor  
ii  ruby  1:2.7+2

-- no debconf information

Bug#969036: linux-image-5.7.0-2-amd64: system does not power off

[Hendrik Tews]

Package: src:linux
Version: 5.7.10-1
Severity: important
X-Debbugs-Cc: none, Hendrik Tews 

Dear Maintainer,

when booting this Linux version with a testing/bullseye
installation, the laptop does not power off on shutdown
(systemctl poweroff) anymore. When booting

  4.19.0-9-amd64 #1 SMP Debian 4.19.118-2+deb10u1 (2020-06-07) x86_64 GNU/Linux

with buster (from a different partition) it does correctly power
off. Some web resources recommend adding "acpi=force" to
GRUB_CMDLINE_LINUX_DEFAULT. This does not help. I would
appreciate any hints or possible workarounds.

Thanks,

Hendrik Tews


-- Package-specific info:
** Version:
Linux version 5.7.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 9.3.0 
(Debian 9.3.0-16), GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 
5.7.10-1 (2020-07-26)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.7.0-2-amd64 root=/dev/mapper/cert--vg-root2 ro quiet

** Not tainted

** Kernel log:
[   10.797787] RAPL PMU: hw unit of domain package 2^-14 Joules
[   10.797788] RAPL PMU: hw unit of domain dram 2^-14 Joules
[   10.797788] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
[   10.797788] RAPL PMU: hw unit of domain psys 2^-14 Joules
[   10.891923] Adding 9764860k swap on /dev/mapper/cert--vg-swap.  Priority:-2 
extents:1 across:9764860k SSFS
[   10.910993] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: 
(null)
[   10.917548] uvcvideo: Found UVC 1.00 device Integrated Camera (04f2:b541)
[   10.929418] uvcvideo: Failed to initialize entity for entity 6
[   10.929419] uvcvideo: Failed to register entities (-22).
[   10.929798] input: Integrated Camera: Integrated C as 
/devices/pci:00/:00:14.0/usb1/1-8/1-8:1.0/input/input15
[   10.929852] usbcore: registered new interface driver uvcvideo
[   10.929853] USB Video Class driver (1.1.1)
[   10.938600] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[   10.940624] Bluetooth: Core ver 2.22
[   10.940632] NET: Registered protocol family 31
[   10.940632] Bluetooth: HCI device and connection manager initialized
[   10.940635] Bluetooth: HCI socket layer initialized
[   10.940636] Bluetooth: L2CAP socket layer initialized
[   10.940638] Bluetooth: SCO socket layer initialized
[   10.943316] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: 
(null)
[   10.993647] usbcore: registered new interface driver btusb
[   11.003472] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC293: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[   11.003474] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   11.003475] snd_hda_codec_realtek hdaudioC0D0:hp_outs=2 
(0x16/0x15/0x0/0x0/0x0)
[   11.003476] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[   11.003477] snd_hda_codec_realtek hdaudioC0D0:inputs:
[   11.003478] snd_hda_codec_realtek hdaudioC0D0:  Dock Mic=0x19
[   11.003479] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a
[   11.003479] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
[   11.008969] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[   11.015593] Bluetooth: hci0: Device revision is 5
[   11.015594] Bluetooth: hci0: Secure boot is enabled
[   11.015595] Bluetooth: hci0: OTP lock is enabled
[   11.015595] Bluetooth: hci0: API lock is enabled
[   11.015596] Bluetooth: hci0: Debug lock is disabled
[   11.015596] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   11.016877] iwlwifi :03:00.0: Detected Intel(R) Dual Band Wireless AC 
8260, REV=0x208
[   11.024646] bluetooth hci0: firmware: direct-loading firmware 
intel/ibt-11-5.sfi
[   11.024649] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[   11.027556] iwlwifi :03:00.0: Applying debug destination EXTERNAL_DRAM
[   11.027728] iwlwifi :03:00.0: Allocated 0x0040 bytes for firmware 
monitor.
[   11.063278] audit: type=1400 audit(1598439368.339:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-senddoc" 
pid=567 comm="apparmor_parser"
[   11.063347] audit: type=1400 audit(1598439368.339:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" 
pid=564 comm="apparmor_parser"
[   11.071470] audit: type=1400 audit(1598439368.347:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="lsb_release" pid=571 
comm="apparmor_parser"
[   11.073447] audit: type=1400 audit(1598439368.351:5): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/sbin/cups-browsed" 
pid=572 comm="apparmor_parser"
[   11.081619] audit: type=1400 audit(1598439368.359:6): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/m

Bug#941544: NMU upload

[Hendrik Tews]

Gard Spreemann  writes:

> If I don't hear back from anyone within three days, my AM will upload
> this NMU in DELAYED/7.

Thanks for working on this. As far as I am concerned, please
upload directly without delay.

Hendrik

Bug#869114: status of the topkg package

[Hendrik Tews]

Andy Li  writes:

> What is the status of the topkg package?

I worked on it last September, see
https://lists.debian.org/debian-ocaml-maint/2017/09/msg00015.html
and https://salsa.debian.org/ocaml-team/ocaml-topkg . I have not
looked into it since then.

Hendrik

Bug#893319: Crash when displaying Unicode 'ALARM CLOCK' (U+23F0) character

[Hendrik Tews]

Another observation: emacs24-x (24.5+1-11+deb9u1) inside Debian
testing does crash on the alarm clock, while the same binary
inside Debian stable (9 - stretch) has no problem with the alarm
clock.

Hendrik

Bug#893319: Crash when displaying Unicode 'ALARM CLOCK' (U+23F0) character

[Hendrik Tews]

The error message pasted by Gaudenz hints at gtk, but gtk can
show the alarm clock (I tried the hello world example from the
tutorial) and emacs25-lucid does also crash, albeit with a
shorter message:

X protocol error: BadLength (poly request too large or internal Xlib 
length error) on protocol request 139

Hendrik

Bug#893319: Crash when displaying Unicode 'ALARM CLOCK' (U+23F0) character

[Hendrik Tews]

I wrote:

 > Gnus is completely unusable for me - emacs dies when I open
 > the first message.

For me the culprit was a spam message containing the ALARM CLOCK
sign in the subject. Gnus therefore crashed emacs when it tried
to display the summary line for that message.

I got around the problem by temporarily deleting ``%s'' (that is,
the subject) from gnus-summary-line-format. Then, carefully
avoiding to show the message, I was able to delete that message
from within the summary buffer.

Hendrik

Bug#893319: Crash when displaying Unicode 'ALARM CLOCK' (U+23F0) character

[Hendrik Tews]

severity 893319 important
thanks

Hi,

I see the same behavior, both with emacs24 and emacs25. And emacs
dies with the same error message in many different circumstances.
Gnus is completely unusable for me - emacs dies when I open the
first message. Raising to important for this reason.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (50, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf, arm64

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages emacs25 depends on:
ii  emacs25-bin-common 25.2+1-6+b1
ii  libacl12.2.52-3+b1
ii  libasound2 1.1.3-5
ii  libatk1.0-02.28.1-1
ii  libc6  2.27-2
ii  libcairo-gobject2  1.15.10-1
ii  libcairo2  1.15.10-1
ii  libdbus-1-31.12.6-2
ii  libfontconfig1 2.12.6-0.1
ii  libfreetype6   2.8.1-2
ii  libgdk-pixbuf2.0-0 2.36.11-1
ii  libgif75.1.4-2
ii  libglib2.0-0   2.54.3-2
ii  libgnutls303.5.18-1
ii  libgomp1   8-20180312-2
ii  libgpm21.20.7-5
ii  libgtk-3-0 3.22.28-1
ii  libice62:1.0.9-2
ii  libjpeg62-turbo1:1.5.2-2+b1
ii  libm17n-0  1.7.0-3+b2
ii  libmagickcore-6.q16-5  8:6.9.9.34+dfsg-3+b1
ii  libmagickwand-6.q16-5  8:6.9.9.34+dfsg-3+b1
ii  libotf00.9.13-3+b1
ii  libpango-1.0-0 1.40.14-1
ii  libpangocairo-1.0-01.40.14-1
ii  libpng16-161.6.34-1
ii  librsvg2-2 2.40.20-2
ii  libselinux12.7-2+b1
ii  libsm6 2:1.2.2-1+b3
ii  libtiff5   4.0.9-4
ii  libtinfo5  6.1-1
ii  libx11-6   2:1.6.4-3
ii  libx11-xcb12:1.6.4-3
ii  libxcb11.13-1
ii  libxfixes3 1:5.0.3-1
ii  libxft22.3.2-1+b2
ii  libxinerama1   2:1.1.3-1+b3
ii  libxml22.9.4+dfsg1-6.1
ii  libxpm41:3.5.12-1
ii  libxrandr2 2:1.5.1-1
ii  libxrender11:0.9.10-1
ii  zlib1g 1:1.2.8.dfsg-5

emacs25 recommends no packages.

Versions of packages emacs25 suggests:
ii  emacs25-common-non-dfsg  25.2+1-1

-- no debconf information

Hendrik

Bug#884454: systemd: systemd udev rule is not executed when removing - only when adding

[Hendrik Tews]

Package: systemd
Version: 235-3
Severity: important

Dear Maintainer,

on my system, systemd_wants udev rules get only executed when I
add devices, not when I remove them.

I have two udev rules

ENV{PRODUCT}=="3/46d/101a/111", TAG+="systemd", ENV{SYSTEMD_WANTS}="aaa"
ENV{PRODUCT}=="3/46d/101a/111", RUN+="/bin/bash -c '/bin/date 
+%%Y-%%m-%%d-%%H:%%M:%%S-RUN >> /tmp/log'"

The product ID belongs to my mouse. The aaa.service contains

[Unit]
Description=AAA

[Service]
Type=simple
ExecStart=/bin/bash -c "/bin/date '+%%Y-%%m-%%d %%H:%%M:%%S AAA' >> 
/tmp/log"

When I unplug the mouse, I only see

2017-12-15-11:40:54-RUN

in /tmp/log. When I plug the mouse, I see

2017-12-15-11:41:22-RUN
2017-12-15 11:41:22 AAA

as expected.

When removing the mouse, the only line in the syslog related to
aaa.service is

Dec 15 11:40:54 cert systemd[1]: aaa.service: Collecting.


I report the problem here for SYSTEMD_WANTS, the same happens for
SYSTEMD_USER_WANTS. I would like to use the latter to run some
command in my X session when the mouse is added and removed.

Thanks for your attention,

Hendrik


-- Package-specific info:

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

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  adduser 3.116
ii  libacl1 2.2.52-3+b1
ii  libapparmor12.11.1-4
ii  libaudit1   1:2.8.1-2
ii  libblkid1   2.30.2-0.1
ii  libc6   2.25-3
ii  libcap2 1:2.25-1.2
ii  libcryptsetup4  2:1.7.5-1
ii  libgcrypt20 1.8.1-4
ii  libgpg-error0   1.27-5
ii  libidn111.33-2
ii  libip4tc0   1.6.1-2+b1
ii  libkmod224-1
ii  liblz4-10.0~r131-2+b1
ii  liblzma55.2.2-1.3
ii  libmount1   2.30.2-0.1
ii  libpam0g1.1.8-3.6
ii  libseccomp2 2.3.1-2.1
ii  libselinux1 2.7-2
ii  libsystemd0 235-3
ii  mount   2.30.2-0.1
ii  procps  2:3.3.12-3
ii  util-linux  2.30.2-0.1

Versions of packages systemd recommends:
ii  dbus1.12.2-1
ii  libpam-systemd  235-3

Versions of packages systemd suggests:
ii  policykit-10.105-18
pn  systemd-container  

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.130
ii  udev 235-3

-- Configuration Files:
/etc/systemd/logind.conf changed:
[Login]
HandleLidSwitch=ignore

/etc/systemd/system.conf changed:
[Manager]
LogLevel=debug


-- no debconf information

Bug#880449: unison: Uncaught exception Failure("input_value: bad bigarray kind")

[Hendrik Tews]

Vincent Lefevre  writes:

> Alternatively, wouldn't it be possible to rename the current unison
> package and make it co-installable with the one from stretch?

Possible maybe, but it wouldn't help. Both packages would be
compiled with the only OCaml compiler available in the current
Debian version, hence both unison's would be incompatible with
the one in stretch.

One side condition that you have to keep in mind is that there
are a lot of architectures and the OCaml team does source
uploads, which get compiled using the current Debian version.

As Stéphane pointed out already: Please discuss with the upstream
authors or submit patches there. Alternatively you could set up
inofficial repository version, where you provide unision packages
compiled with different OCaml versions.

Hendrik

Bug#876533: hol-light FTBFS with OCaml 4.05.0

[Hendrik Tews]

> Hi Hendrik, any progress on this? I notice in the ocaml transition tracker:

I really spend more than 4 weeks in discussions with upstream
about license and copyright clarifications. Now it is finished. I
uploaded a new hol-light version to DOM git yesterday. Please
review and upload.

If you think I fulfill the conditions for directly uploading
hol-light, I would appreciate, if somebody could execute

dcut dm --uid "Hendrik Tews" --allow hol-light

Bye,

Hendrik

Bug#878968: libglvnd0-nvidia: undefined symbol: _glapi_tls_Current makes system unusable

[Hendrik Tews]

> Please attach the full report by running
>
> reportbug --template nvidia-driver

I am not sure this helps, but here you go. This is the result
that ``reportbug --template nvidia-driver'' saved in /tmp:

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Hendrik Tews <hend...@askra.de>
To: Debian Bug Tracking System <sub...@bugs.debian.org>
Subject: nvidia-driver: none

Package: nvidia-driver
Severity: wishlist

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
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)

Bug#878968: libglvnd0-nvidia: undefined symbol: _glapi_tls_Current makes system unusable

[Hendrik Tews]

Package: libglvnd0-nvidia
Version: 375.82-5
Severity: critical

Dear Maintainer,

after updating some packages this morning, X11 did not come up
any more and the system was completely unusable. Apparently gdm
was restarting continuously, making it impossible to enter
anything in a terminal window. I needed to boot in recovery mode
to get access again.

The syslog contains

/usr/lib/gdm3/gdm-x-session[2703]: (EE) Failed to load 
/usr/lib/xorg/modules/extensions/libglx.so: 
/usr/lib/x86_64-linux-gnu/libGL.so.1: undefined symbol: _glapi_tls_Current

and I get the same undefined symbol error when I try startx.

After installing libglvnd0 (and purging libglvnd0-nvidia)
everything is fine again. In contrast to what is reported in
https://lists.debian.org/debian-kde/2017/10/msg00028.html, the
problem appears again, when I reinstall libglvnd0-nvidia.

Bye,

Hendrik


-- Package-specific info:
uname -a:
Linux cert 4.13.0-1-amd64 #1 SMP Debian 4.13.4-1 (2017-10-01) x86_64 GNU/Linux

/proc/version:
Linux version 4.13.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 
6.4.0 20170920 (Debian 6.4.0-7)) #1 SMP Debian 4.13.4-1 (2017-10-01)

lspci 'VGA compatible controller [0300]':
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 
[8086:191b] (rev 06) (prog-if 00 [VGA controller])
Subsystem: Lenovo HD Graphics 530 [17aa:5056]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

dmesg:

Device node permissions:
crw-rw+ 1 root video 226,   0 Oct 17 21:58 /dev/dri/card0
crw-rw+ 1 root video 226, 128 Oct 17 21:58 /dev/dri/renderD128

/dev/dri/by-path:
total 0
lrwxrwxrwx 1 root root  8 Oct 17 21:58 pci-:00:02.0-card -> ../card0
lrwxrwxrwx 1 root root 13 Oct 17 21:58 pci-:00:02.0-render -> ../renderD128
video:x:44:tews

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root 15 Sep 28 22:04 
/usr/lib/x86_64-linux-gnu/libEGL.so.1 -> libEGL.so.1.0.0
-rw-r--r-- 1 root root  76344 Sep 28 22:04 
/usr/lib/x86_64-linux-gnu/libEGL.so.1.0.0
lrwxrwxrwx 1 root root 14 Sep 28 22:04 /usr/lib/x86_64-linux-gnu/libGL.so.1 
-> libGL.so.1.0.0
-rw-r--r-- 1 root root 567624 Sep 28 22:04 
/usr/lib/x86_64-linux-gnu/libGL.so.1.0.0
lrwxrwxrwx 1 root root 18 Sep 28 22:04 
/usr/lib/x86_64-linux-gnu/libGLESv2.so.2 -> libGLESv2.so.2.0.0
-rw-r--r-- 1 root root  55616 Sep 28 22:04 
/usr/lib/x86_64-linux-gnu/libGLESv2.so.2.0.0
-rw-r--r-- 1 root root 29 Jul  7 07:31 
/usr/lib/xorg/modules/extensions/libglx.so
-rw-r--r-- 1 root root   5883 Oct 17 09:07 /var/log/Xorg.0.log

/etc/modprobe.d:
total 24
drwxr-xr-x   2 root root  4096 Sep 18 13:14 .
drwxr-xr-x 162 root root 12288 Oct 17 21:55 ..
-rw-r--r--   1 root root   154 Nov 30  2016 amd64-microcode-blacklist.conf
-rw-r--r--   1 root root   154 Nov  9  2016 intel-microcode-blacklist.conf


/etc/modules-load.d:
-rw-r--r-- 1 root root  195 Mar  1  2017 /etc/modules

/etc/modules-load.d/:
total 20
drwxr-xr-x   2 root root  4096 Oct 17 08:42 .
drwxr-xr-x 162 root root 12288 Oct 17 21:55 ..
-rw-r--r--   1 root root   119 Jan 19  2017 cups-filters.conf
lrwxrwxrwx   1 root root10 Oct 11 00:46 modules.conf -> ../modules


Files from nvidia-installer:

Config and logfiles:

<< /home/tews/.local/share/xorg/Xorg.0.log >>
[32.985] 
X.Org X Server 1.19.3
Release Date: 2017-03-15
[32.991] X Protocol Version 11, Revision 0
[32.992] Build Operating System: Linux 4.9.0-3-amd64 x86_64 Debian
[32.994] Current Operating System: Linux cert 4.13.0-1-amd64 #1 SMP Debian 
4.13.4-1 (2017-10-01) x86_64
[32.994] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.13.0-1-amd64 
root=/dev/mapper/cert--vg-root1 ro single
[32.998] Build Date: 07 July 2017  06:22:09AM
[33.000] xorg-server 2:1.19.3-2 (https://www.debian.org/support) 
[33.001] Current version of pixman: 0.34.0
[33.005]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[33.005] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[33.012] (==) Log file: "/home/tews/.local/share/xorg/Xorg.0.log", Time: 
Tue Oct 17 21:58:39 2017
[33.019] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[33.024] (==) No Layout section.  Using the first Screen section.
[33.024] (==) No screen section available. Using defaults.
[33.024] (**) |-->Screen "Default Screen Section" (0)
[33.024] (**) |   |-->Monitor ""
[33.024] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[33.024] (==) Automatically adding devices
[33.024] (==) Automatically enabling 

Bug#878615: hol-light: installs .pc/ files into a binary package

[Hendrik Tews]

Thanks for the note! I'll take care of it in the next version.

Hendrik

Bug#876533: hol-light FTBFS with OCaml 4.05.0

[Hendrik Tews]

Upstream does indeed fix this problem. However, it also contains
a few files with unclear license and copyright, currently
preventing to package it. I am trying to solve these license and
copyright issues with upstream.

Hendrik

Bug#876537: otags FTBFS with OCaml 4.05.0

[Hendrik Tews]

Yesterday, I prepared a new otags package that builds fine with
4.05, see
https://lists.debian.org/debian-ocaml-maint/2017/09/msg00079.html
and
https://anonscm.debian.org/gitweb/?p=pkg-ocaml-maint/packages/otags.git .
The only thing that is missing now is somebody who sponsors an
upload.

Hendrik

Bug#876533: hol-light FTBFS with OCaml 4.05.0

[Hendrik Tews]

I have a look at it, hopefully a new upstream version will fix
the problem.

Hendrik

Bug#869114: ITP: ocaml-libtopkg -- packager for distributing OCaml software

[Hendrik Tews]

Hi,

with great help from the upstream author, the cyclic build
dependency has been solved now. However, I still only intend to
package the topkg packaging library and not the topkg-care tool,
because the latter has a number of build dependencies that are
not (yet) available in Debian.

I intend to name the source package ocaml-topkg with binary
packages libtopkg-ocaml and libtopkg-ocaml-dev, if needed.

Regards,

Hendrik

Bug#869114: ITP: ocaml-libtopkg -- packager for distributing OCaml software

[Hendrik Tews]

Package: wnpp
Owner: Hendrik Tews <hend...@askra.de>
Severity: wishlist

* Package name: ocaml-libtopkg
  Version : 0.9.0
  Upstream Author : Daniel Bünzli
* URL or Web page : http://erratique.ch/software/topkg
* License : ISC
  Programming Lang: OCaml
  Description : packager for distributing OCaml software

Topkg is a packager for distributing OCaml software. It provides
an API to describe the files a package installs in a given build
configuration and to specify information about the package's
distribution creation and publication procedures.

Topkg is needed as build dependency for new upstream versions of
existing OCaml packages, for instance cmdliner. The topkg
upstream sources do also contain topkg-care, a command line tool
that helps with various aspects of a package's life cycle.
However, topkg-care has various build dependencies, among them
cmdliner. Therefore, the ocaml-libtopkg source package won't
build topkg-care. If we need topkg-care in Debian, it should go
into a separate source package with identical upstream tar ball.

Regards,

Hendrik

Bug#868606: hol-light FTBFS: Error: This expression has type (MLast.loc * string Ploc.vala) Ploc.vala but an expression was expected of type MLast.loc * 'a

[Hendrik Tews]

> Some recent change in unstable make hol-light FTBFS:

I blame the new camlp5 version for this. I have to see if
upstream supports camlp5 version 7 already.

Hendrik

Bug#774553: exim4: Do not scan outgoing mail for spam

[Hendrik Tews]

Hi,

could you please include this patch or something similar? I also
followed the suggestion in the Debian exim config files and, as a
result, produced non-conform messages that were discarded by some
other servers.

Note that the Debian exim wiki contains the same wrong advice.

Thanks,

Hendrik

Bug#543548: coq-doc-pdf: bookmarks and links for table of contents

[Hendrik Tews]

found 543548 coq-doc/8.4pl4-2
forwarded 543548 https://coq.inria.fr/bugs/show_bug.cgi?id=5636
thanks

Hi,

as others have noticed, the reference manual contains the
bookmarks and the links for some while already. However, the FAQ,
the Tutorial and the RecTutorial do not.

Hendrik

Bug#861889: apt: apt.systemd.daily runs before network comes up

[Hendrik Tews]

> Note that this only applies on boot. Resume does not work.

What do you mean with "Resume does not work"? I usually wake up
my laptop from suspend or hibernate in the morning, then
apt.systemd.daily runs before the network comes up. Now and then
I reboot the system later, but then the time stamps prevent
apt.system.daily from doing anything.

> You could look at 
>
>  /var/lib/systemd/deb-systemd-helper-enabled/network-online.target.wants/
>  /{usr/,}lib/systemd/system/network-online.target.wants/ 
>  /etc/systemd/system/network-online.target.wants

I have the first and the last and they both contain files
networking.service and NetworkManager-wait-online.service and I
use NetworkManager.

Thanks,

Hendrik

Bug#861889: apt: apt.systemd.daily runs before network comes up

[Hendrik Tews]

Julian,

thanks a lot for you quick answer.

> Check that your network-online target actually ensures that the
> network is up. (the service might want to depend on that as

I have no idea how to check this. Could you point me to a
relevant HowTo?

Thanks,

Hendrik

Bug#861889: apt: apt.systemd.daily runs before network comes up

[Hendrik Tews]

Package: apt
Version: 1.4.1
Severity: normal

Dear Maintainer,

I configured

APT::Periodic::Enable "1";
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Download-Upgradeable-Packages "1";

but apt almost never downloads anything automatically. The reason
is that systemd runs apt.systemd.daily before the network comes
up.

Bye,

Hendrik

-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "1";
APT::Install-Suggests "0";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-4\.9\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-image-4\.9\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.9\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.9\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.9\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.9\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.9\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.9\.0-2-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.9\.0-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.9\.0-2-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.9\.0-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.9\.0-2-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.9\.0-1-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.9\.0-2-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.9\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.9\.0-2-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.9\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.9\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.9\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.9\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-tools-4\.9\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-tools-4\.9\.0-2-amd64$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-image";
APT::VersionedKernelPackages:: "linux-headers";
APT::VersionedKernelPackages:: "linux-image-extra";
APT::VersionedKernelPackages:: "linux-signed-image";
APT::VersionedKernelPackages:: "kfreebsd-image";
APT::VersionedKernelPackages:: "kfreebsd-headers";
APT::VersionedKernelPackages:: "gnumach-image";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::VersionedKernelPackages:: "linux-backports-modules-.*";
APT::VersionedKernelPackages:: "linux-tools";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "contrib/metapackages";
APT::Never-MarkAuto-Sections:: "non-free/metapackages";
APT::Never-MarkAuto-Sections:: "restricted/metapackages";
APT::Never-MarkAuto-Sections:: "universe/metapackages";
APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
APT::Move-Autobit-Sections "";
APT::Move-Autobit-Sections:: "oldlibs";
APT::Move-Autobit-Sections:: "contrib/oldlibs";
APT::Move-Autobit-Sections:: "non-free/oldlibs";
APT::Move-Autobit-Sections:: "restricted/oldlibs";
APT::Move-Autobit-Sections:: "universe/oldlibs";
APT::Move-Autobit-Sections:: "multiverse/oldlibs";
APT::Periodic "";
APT::Periodic::Enable "1";
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Download-Upgradeable-Packages "1";
APT::Periodic::Verbose "1";
APT::Periodic::Unattended-Upgrade "1";
APT::Update "";
APT::Update::Post-Invoke-Success "";
APT::Update::Post-Invoke-Success:: "/usr/bin/test -e 
/usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && 
/usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call 
--system --dest org.freedesktop.PackageKit --object-path 
/org/freedesktop/PackageKit --timeout 4 --method 
org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo 
> /dev/null";
APT::Update::Post-Invoke-Success:: "if /usr/bin/test -w /var/cache/app-info -a 
-e /usr/bin/appstreamcli; then appstreamcli refresh-cache > /dev/null; fi";
APT::Architectures "";
APT::Architectures:: "amd64";
APT::Architectures:: "armhf";
APT::Architectures:: "arm64";
APT::Compressor "";
APT::Compressor::. "";
APT::Compressor::.::Name ".";
APT::Compressor::.::Extension "";
APT::Compressor::.::Binary "";
APT::Compressor::.::Cost "0";
APT::Compressor::lz4 "";
APT::Compressor::lz4::Name "lz4";
APT::Compressor::lz4::Extension ".lz4";
APT::Compressor::lz4::Binary "false";
APT::Compressor::lz4::Cost "50";
APT::Compressor::gzip "";
APT::Compressor::gzip::Name "gzip";
APT::Compressor::gzip::Extension ".gz";
APT::Compressor::gzip::Binary "gzip";
APT::Compressor::gzip::Cost "100";
APT::Compressor::gzip::CompressArg "";
APT::Compressor::gzip::CompressArg:: "-6n";
APT::Compressor::gzip::UncompressArg "";
APT::Compressor::gzip::UncompressArg:: "-d";
APT::Compressor::xz "";

Bug#856919: [Pkg-utopia-maintainers] Bug#856919: network-manager: ignores high priority of wired connection

[Hendrik Tews]

Hi,

Michael Biebl  writes:

> afaiu, the priority is used to decide which connection profile to use if
> there are multiple profiles available which could be applied for a given
> device. In your case the different profiles do not apply to the same
> devices, as they have differen types (type=wired, type=wifi)

If this is true, then there is at least a documentation problem,
because nm-settings(5) says

If the connection is set to autoconnect, connections with higher
priority will be preferred. Defaults to 0. The higher number
means higher priority.

without any restriction to the same device.

Nevertheless it would be nice, if network-manager would use the
autoconnect-priority for all devices, because alternative
solutions are quite awkward.

Hendrik

Bug#856919: network-manager: ignores high priority of wired connection

[Hendrik Tews]

Package: network-manager
Version: 1.6.2-1
Severity: normal

Dear Maintainer,

I have a wired and a wireless connections configured. The wired
has autoconnect-priority=100 and the wired has
autoconnect-priority=50. However, when I set both connections to
autoconnect=true, network-manager will enable both connections
when both are available. I would have expected that it only
enables the connection with the highest priority.

Hendrik


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages network-manager depends on:
ii  adduser3.115
ii  dbus   1.10.16-1
ii  init-system-helpers1.47
ii  libaudit1  1:2.6.7-1
ii  libbluetooth3  5.43-1
ii  libc6  2.24-9
ii  libglib2.0-0   2.50.3-1
ii  libgnutls303.5.8-3
ii  libgudev-1.0-0 230-3
ii  libjansson42.9-1
ii  libmm-glib01.6.4-1
ii  libndp01.6-1+b1
ii  libnewt0.520.52.19-1+b1
ii  libnl-3-2003.2.27-1+b1
ii  libnm0 1.6.2-1
ii  libpam-systemd 232-18
ii  libpolkit-agent-1-00.105-17
ii  libpolkit-gobject-1-0  0.105-17
ii  libreadline7   7.0-2
ii  libselinux12.6-3
ii  libsoup2.4-1   2.56.0-2
ii  libsystemd0232-18
ii  libteamdctl0   1.26-1+b1
ii  libuuid1   2.29.1-1
ii  lsb-base   9.20161125
ii  policykit-10.105-17
ii  udev   232-18
ii  wpasupplicant  2.5-2+v2.4-3+b1

Versions of packages network-manager recommends:
ii  crda 3.18-1
ii  dnsmasq-base 2.76-5
ii  iptables 1.6.0+snapshot20161117-5
ii  iputils-arping   3:20161105-1
ii  isc-dhcp-client  4.3.5-3
ii  modemmanager 1.6.4-1
ii  ppp  2.4.7-1+4

Versions of packages network-manager suggests:
pn  libteam-utils  

-- no debconf information

Bug#856644: software-properties-common: add-apt-repository: Exception in thread Thread-1

[Hendrik Tews]

Package: software-properties-common
Version: 0.96.20.2-1
Severity: normal

Dear Maintainer,

when I run "sudo add-apt-repository ppa:nextcloud-devs/client"
(after manually installing dirmngr), I get

 The Nextcloud desktop client compiled for Ubuntu
 More info: https://launchpad.net/~nextcloud-devs/+archive/ubuntu/client
Press [ENTER] to continue or ctrl-c to cancel adding it

gpg: keybox '/tmp/tmpq1gq3lbf/pubring.gpg' created
gpg: /tmp/tmpq1gq3lbf/trustdb.gpg: trustdb created
gpg: key 60EE47FBAD3DD469: public key "Launchpad PPA for Nextcloud 
development" imported
gpg: Total number processed: 1
gpg:   imported: 1
gpg: no valid OpenPGP data found.
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python3.5/threading.py", line 914, in _bootstrap_inner
self.run()
  File "/usr/lib/python3.5/threading.py", line 862, in run
self._target(*self._args, **self._kwargs)
  File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
688, in addkey_func
func(**kwargs)
  File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 
386, in add_key
return apsk.add_ppa_signing_key()
  File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 
273, in add_ppa_signing_key
cleanup(tmp_keyring_dir)
  File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 
234, in cleanup
shutil.rmtree(tmp_keyring_dir)
  File "/usr/lib/python3.5/shutil.py", line 480, in rmtree
_rmtree_safe_fd(fd, path, onerror)
  File "/usr/lib/python3.5/shutil.py", line 438, in _rmtree_safe_fd
onerror(os.unlink, fullname, sys.exc_info())
  File "/usr/lib/python3.5/shutil.py", line 436, in _rmtree_safe_fd
os.unlink(name, dir_fd=topfd)
FileNotFoundError: [Errno 2] No such file or directory: 'S.gpg-agent.ssh'

I believe this happend because there were no pgp files or key
directories in my account. After importing a key, the command
runs fine.

Greetings,

Hendrik

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages software-properties-common depends on:
ii  ca-certificates  20161130
ii  gir1.2-glib-2.0  1.50.0-1+b1
ii  gir1.2-packagekitglib-1.01.1.5-1
ii  python-apt-common1.4.0~beta2
ii  python3  3.5.3-1
ii  python3-dbus 1.2.4-1
ii  python3-gi   3.22.0-2
ii  python3-software-properties  0.96.20.2-1
pn  python3:any  

Versions of packages software-properties-common recommends:
ii  packagekit  1.1.5-1

software-properties-common suggests no packages.

-- no debconf information

Bug#856643: software-properties-common: missing dependency on dirmngr

[Hendrik Tews]

Package: software-properties-common
Version: 0.96.20.2-1
Severity: normal

Dear Maintainer,

when I run "sudo add-apt-repository ppa:nextcloud-devs/client",
I see

 The Nextcloud desktop client compiled for Ubuntu
 More info: https://launchpad.net/~nextcloud-devs/+archive/ubuntu/client
Press [ENTER] to continue or ctrl-c to cancel adding it

gpg: keybox '/tmp/tmp_f8_idm1/pubring.gpg' created
gpg: failed to start the dirmngr '/usr/bin/dirmngr': No such file or 
directory
gpg: connecting dirmngr at '/tmp/tmp_f8_idm1/S.dirmngr' failed: No such 
file or directory
gpg: keyserver receive failed: No dirmngr

I believe there is a dependency on dirmngr missing.

Greetings,

Hendrik

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages software-properties-common depends on:
ii  ca-certificates  20161130
ii  gir1.2-glib-2.0  1.50.0-1+b1
ii  gir1.2-packagekitglib-1.01.1.5-1
ii  python-apt-common1.4.0~beta2
ii  python3  3.5.3-1
ii  python3-dbus 1.2.4-1
ii  python3-gi   3.22.0-2
ii  python3-software-properties  0.96.20.2-1
pn  python3:any  

Versions of packages software-properties-common recommends:
ii  packagekit  1.1.5-1

software-properties-common suggests no packages.

-- no debconf information

Bug#854147: coq: ERROR: coq is broken - called emacs-package-install as a new-style add-on, but has no compat file.

[Hendrik Tews]

Hi,

I would say, this is not really critical. As far as I understand,
the emacs compat file is a policy requirement, which is not used
currently.

The fix is easy, just include a file .emacsen-compat
with content 0 in the debian directory, see for instance
https://alioth.debian.org/scm/viewvc.php/emacs-goodies-el/debian/debian-el.emacsen-compat?root=pkg-goodies-el=log
and /usr/lib/emacsen-common/packages/compat in your local debian
installation.

Hendrik

Bug#843319: FTBFS: libsexplib-camlp4-dev is no longer available

[Hendrik Tews]

Hi,

AFAIR the libsexplib dependency is only used for testing after
building. It can safely be removed when the the tests are
disabled (or when those files that depend on libsexplib have been
removed from the Makefile).

Bye,

Hendrik

Bug#831566: Acknowledgement (proofgeneral/testing does not support the full syntax of coq/testing)

[Hendrik Tews]

Hi,

Samuel Hym  writes:

> Could the debian package be updated?

Thanks for the reminder, I'll have a look if time permits, but if
anybody else want to upload a new version, please go ahead.

Hendrik

Bug#784328: FVWM: fvwm hotkey problem inside vnc

[Hendrik Tews]

Hi,

Thomas Adam <tho...@fvwm.org> writes:

> On 28 February 2016 at 23:05, Hendrik Tews <hendrik.t...@fireeye.com> wrote:
>> The XKEYBOARD doc clearly say, no Xkb function should be called
>> if the server does not provide XKEYBOARD. And indeed, inside
>> vnc4server, XkbKeycodeToKeysym does always return 0. (I attach a
>> small test program that shows this behavior.) Inside the loop in
>> AddBinding (file libs/Binding.c) this causes all key bindings to
>> be dropped.
>
> So?  There is nothing FVWM can do about this.  Nor should it.  If you

Fvwm could and should use the XKEYBOARD extension properly, which
means, check at runtime if XKEYBOARD is supported in the server
and disable all XKEYBOARD calls if the result is negative. I
believe the XKEYBOARD documentation is very clear on this. The
Debian version of Fvwm has definitely a deficiency on this point.
And, as far as I understand, your github Fvwm version could also
be improved here.

> really don't want to use XKB at all with FVWM, then you can undefine
> 'HAVE_X11_XKBLIB_H' -- which will force FVWM to use
> XKeycodeToKeysym().

This is not a solution, because it would require me to keep two
compiled versions of Fvwm around. One for using on ordinary
displays and one for using inside vnc.

>> As conclusion, there are the following solutions to this problem:
>>
>> - downgrade to Debian fvwm 2.5.30 (as suggested by Claude)
>>   because this uses XKeycodeToKeysym
>
> No.  See suggestion above.

This is definitely a solution. And for Debian users it is still
the simplest one.

>> - compile fvwm without the offending patch, for instance the
>
> No.  Just use CVS.  Oh, and see above.

What do you mean by no? This is of course a solution. And you are
contradicting yourself here, because using CVS means compiling
Fvwm without the offending patch.

Bye,

Hendrik
This email and any attachments thereto may contain private, confidential, 
and/or privileged material for the sole use of the intended recipient. Any 
review, copying, or distribution of this email (or any attachments thereto) by 
others is strictly prohibited. If you are not the intended recipient, please 
contact the sender immediately and permanently delete the original and any 
copies of this email and any attachments thereto.

Bug#784328: FVWM: fvwm hotkey problem inside vnc

[Hendrik Tews]

Hendrik Tews <hendrik.t...@fireeye.com> writes:

> I found the culprit: It's the Debian deprecated.patch, which I
> attach below, in case you are interested.

I analyzed the problem a bit further. The patch deprecated.patch
replaces various occurrences of XKeycodeToKeysym with
XkbKeycodeToKeysym, apparently following various resources
suggesting XkbKeycodeToKeysym should be used instead of the
deprecated XKeycodeToKeysym. The problem is that these
suggestions are wrong wrt. applications running inside X servers
without the XKEYBOARD extension and vnc4server _does not_ have
the XKEYBOARD extension.

The XKEYBOARD doc clearly say, no Xkb function should be called
if the server does not provide XKEYBOARD. And indeed, inside
vnc4server, XkbKeycodeToKeysym does always return 0. (I attach a
small test program that shows this behavior.) Inside the loop in
AddBinding (file libs/Binding.c) this causes all key bindings to
be dropped.

For the behavior of XkbKeycodeToKeysym it is not relevant whether
the XKEYBOARD extension is properly initialized or not (indeed,
the patch uses XkbKeycodeToKeysym without calling
XkbQueryExtension as the documentation requests).

Therefore, I strongly believe that as long as Debian distributes
X servers without the XKEYBOARD extension, such as vnc4server for
example, fvwm should use the deprecated XKeycodeToKeysym instead
of XkbKeycodeToKeysym. As a consequence, the patch
deprecated.patch should be removed.

As conclusion, there are the following solutions to this problem:

- downgrade to Debian fvwm 2.5.30 (as suggested by Claude)
  because this uses XKeycodeToKeysym

- use a vnc server with XKEYBOARD, such as tigervnc

- compile fvwm without the offending patch, for instance the
  upstream version (the Debian package lists debhelper (>=
  9.0.0), autotools-dev, dh-autoreconf, file, fontconfig,
  gettext, libfontconfig1-dev | libfontconfig-dev,
  libfreetype6-dev, libfribidi-dev (>= 0.10.7), libncurses5-dev,
  libreadline-dev | libreadline6-dev | libreadline5-dev,
  libpng12-dev | libpng-dev, librplay3-dev, librsvg2-dev (>=
  2.13.92), libsm-dev, libstroke0-dev, libx11-dev,
  libxcursor-dev, libxext-dev, libxft-dev, libxi-dev,
  libxinerama-dev, libxpm-dev, libxrandr-dev, libxrender-dev,
  libxt-dev, sharutils, xsltproc as build dependencies).

Bye,

Hendrik


This email and any attachments thereto may contain private, confidential, 
and/or privileged material for the sole use of the intended recipient. Any 
review, copying, or distribution of this email (or any attachments thereto) by 
others is strictly prohibited. If you are not the intended recipient, please 
contact the sender immediately and permanently delete the original and any 
copies of this email and any attachments thereto.

#include 
#include 
#include 
#include 

int main(int argc, char **argv)
{
  char *display_name = NULL;
  Display * dpy;
  int xkb_major = XkbMajorVersion;
  int xkb_minor = XkbMinorVersion;
  int xkb_opcode, xkb_event_base, xkb_error_base, xkb_open_reason;

  dpy = XOpenDisplay(display_name);
  if (!dpy) {
fprintf(stderr, "xkbtest: unable to open display '%s'\n",
  	XDisplayName (display_name));
exit(2);
  }
  
  printf("Connected\n");
  
  if(XkbLibraryVersion(_major, _minor)) {
printf("linked with compatible XKB lib %d.%d\n", xkb_major, xkb_minor);
  } else {
fprintf(stderr, "xkbtest: dynamic XKB library incompatible\n");
exit(2);
  }
  
  xkb_major = XkbMajorVersion;
  xkb_minor = XkbMinorVersion;
  if(XkbQueryExtension(dpy, _opcode, _event_base, _error_base,
  		   _major, _minor)) {
printf("compatible XKB on server present version %d.%d\n"
  	   "opcode %d ev base %d error base %d\n",
  	   xkb_major, xkb_minor, xkb_opcode, xkb_event_base, xkb_error_base);
  } else {
printf("no compatible XKB on server\n");
  }

  printf("key 0x48 index 0 to keysym std: %lX\n",
	 XKeycodeToKeysym(dpy, 0x48, 0));

  printf("key 0x48 group 0 index 0 to keysym XKB: %lX\n",
	 XkbKeycodeToKeysym(dpy, 0x48, 0, 0));
  
  return 0;
}


/*** 
Local Variables:
compile-command: "gcc -Wall -o xkbtest -lX11 xkbtest.c"
End:
***/

Bug#784328: FVWM: fvwm hotkey problem inside vnc

[Hendrik Tews]

Here is the patch. To me it looks like these changes have been
introduced in the first 2.6.5 Debian package.

Bye,

Hendrik

This email and any attachments thereto may contain private, confidential, 
and/or privileged material for the sole use of the intended recipient. Any 
review, copying, or distribution of this email (or any attachments thereto) by 
others is strictly prohibited. If you are not the intended recipient, please 
contact the sender immediately and permanently delete the original and any 
copies of this email and any attachments thereto.
>From 06234f650ab35da27489ed71fee67d024391f80d Mon Sep 17 00:00:00 2001
From: tadam 
Subject: [PATCH] Provide fvwm_KeycodeToKeysym() to handle XKeycodeToKeysym()
 deprecation

X are deprecating XKeycodeToKeysym() in favour of XkbKeycodeToKeysym() --
however, older XServers will obviously not have access to XKB, so we have to
conditionally use the newer method only when it's available.

Origin: backport, https://github.com/ThomasAdam/fvwm/commit/06234f650ab35da27489ed71fee67d024391f80d.patch
Last-Update: 2013-02-02
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
 
diff --git a/configure.ac b/configure.ac
index 9588bbb..9f6db24 100644
--- a/configure.ac
+++ b/configure.ac
@@ -537,7 +537,11 @@ if test ! x"$with_shm" = xno; then
[$X_LIBS $X_PRE_LIBS -lX11 $X_EXTRA_LIBS])
 fi
 
-# * xinerama
+# Silently look for X11/XKBlib.h
+AH_TEMPLATE([HAVE_X11_XKBLIB_H],[Define if Xkb extension is used.])
+AC_CHECK_HEADER(X11/XKBlib.h, AC_DEFINE(HAVE_X11_XKBLIB_H))
+
+# * xineramA
 problem_xinerama=""
 
 AC_ARG_ENABLE(xinerama,
@@ -1657,6 +1661,14 @@ AH_VERBATIM([_ZEND_EXPLICIT_DEFINITIONS],
 #define fvwm_lstat(x,y) -1
 #endif
 
+#ifdef HAVE_X11_XKBLIB_H
+#include 
+#define fvwm_KeycodeToKeysym(d, k, g, l) \
+	(XkbKeycodeToKeysym((d), (k), (g), (l)))
+#else
+#define fvwm_KeycodeToKeysym(d, k, x, i) (XKeycodeToKeysym((d), (k), (i)))
+#endif
+
 ])
 
 # mainly for fvwm-config
diff --git a/fvwm/builtins.c b/fvwm/builtins.c
index 8cb39e5..199a323 100644
--- a/fvwm/builtins.c
+++ b/fvwm/builtins.c
@@ -3853,7 +3853,7 @@ static Bool FKeysymToKeycode (Display *dpy, KeySym keysym,
 
 	for (m = 0; m <= 8; ++m)
 	{
-		KeySym ks = XKeycodeToKeysym(dpy, *keycode, m);
+		KeySym ks = fvwm_KeycodeToKeysym(dpy, *keycode, 0, m);
 		if (ks == keysym)
 		{
 			switch (m)
diff --git a/fvwm/events.c b/fvwm/events.c
index e6a1a74..cd25caf 100644
--- a/fvwm/events.c
+++ b/fvwm/events.c
@@ -2508,7 +2508,7 @@ void __handle_key(const evh_args_t *ea, Bool is_press)
 	/* Here's a real hack - some systems have two keys with the
 	 * same keysym and different keycodes. This converts all
 	 * the cases to one keycode. */
-	kc = XKeysymToKeycode(dpy, XKeycodeToKeysym(dpy, te->xkey.keycode, 0));
+	kc = XKeysymToKeycode(dpy, fvwm_KeycodeToKeysym(dpy, te->xkey.keycode, 0, 0));
 
 	/* Check if there is something bound to the key */
 
diff --git a/libs/Bindings.c b/libs/Bindings.c
index f024659..d7f76e6 100644
--- a/libs/Bindings.c
+++ b/libs/Bindings.c
@@ -181,7 +181,7 @@ int AddBinding(
 		{
 			if (BIND_IS_MOUSE_BINDING(type) ||
 			STROKE_CODE(BIND_IS_STROKE_BINDING(type) ||)
-			(tkeysym = XKeycodeToKeysym(dpy, i, m)) == keysym)
+			(tkeysym = fvwm_KeycodeToKeysym(dpy, i, 0, m)) == keysym)
 			{
 unsigned int add_modifiers = 0;
 unsigned int bind_mask = 1;
diff --git a/modules/FvwmIconBox/FvwmIconBox.c b/modules/FvwmIconBox/FvwmIconBox.c
index ef8c237..700cae0 100644
--- a/modules/FvwmIconBox/FvwmIconBox.c
+++ b/modules/FvwmIconBox/FvwmIconBox.c
@@ -2445,7 +2445,7 @@ void parsekey(char *tline)
 
   XDisplayKeycodes(dpy, , );
   for (i=kmin; i<=kmax; i++)
-if (XKeycodeToKeysym(dpy, i, 0) == keysym)
+if (fvwm_KeycodeToKeysym(dpy, i, 0, 0) == keysym)
   {
 	k = (struct keyfunc *)safemalloc(sizeof(struct keyfunc));
 	memset(k, 0, sizeof(struct keyfunc));
@@ -3421,7 +3421,7 @@ void ExecuteKey(XEvent event)
 
   tmp = KeyActions;
   event.xkey.keycode =
-XKeysymToKeycode(dpy,XKeycodeToKeysym(dpy,event.xkey.keycode,0));
+XKeysymToKeycode(dpy,fvwm_KeycodeToKeysym(dpy,event.xkey.keycode,0,0));
   while (tmp != NULL){
 if (tmp->keycode == event.xkey.keycode){
   MySendFvwmPipe(fd, tmp->action, item->id);
diff --git a/modules/FvwmIconMan/readconfig.c b/modules/FvwmIconMan/readconfig.c
index e6ddd79..2bf6cda 100644
--- a/modules/FvwmIconMan/readconfig.c
+++ b/modules/FvwmIconMan/readconfig.c
@@ -753,7 +753,7 @@ static Binding *ParseKeyEntry(char *tline)
 
   XDisplayKeycodes(theDisplay, , );
   for (i=min; i<=max; i++) {
-if (XKeycodeToKeysym(theDisplay, i, 0) == keysym) {
+if (fvwm_KeycodeToKeysym(theDisplay, i, 0, 0) == keysym) {
   if (!func) {
 	func = parse_function_list(action);
 	if (!func) {
diff --git a/modules/FvwmIconMan/x.c b/modules/FvwmIconMan/x.c
index 97a8a43..4c98375 100644
--- a/modules/FvwmIconMan/x.c
+++ b/modules/FvwmIconMan/x.c
@@ -245,8 +245,8 @@ void xevent_loop (void)
* the 

Bug#784328: FVWM: fvwm hotkey problem inside vnc

[Hendrik Tews]

I found the culprit: It's the Debian deprecated.patch, which I
attach below, in case you are interested.

This means it's a Debian packaging bug. Debian applies this
deprecated.patch during build, thereby apparently making fvwm
incompatible with the X xerver running inside vnc.

In retrospect, I should have earlier tried to confirm whether the
problem is present at all in the upstream fvwm version. However,
I was under the wrong impression that Debian distributes an
almost unmodified fvwm (the opposite is true - there are 12
Debian patches). Further, also the email from Raphael in March on
the fvwm list gave me the impression somebody has checked this
with upstream fvwm.

Bye,

Hendrik

This email and any attachments thereto may contain private, confidential, 
and/or privileged material for the sole use of the intended recipient. Any 
review, copying, or distribution of this email (or any attachments thereto) by 
others is strictly prohibited. If you are not the intended recipient, please 
contact the sender immediately and permanently delete the original and any 
copies of this email and any attachments thereto.

Bug#784328: FVWM: fvwm hotkey problem inside vnc

[Hendrik Tews]

Dan Espen  writes:

> On the Debian list they say:
>
>   So after  all, this  bug may have  been triggered by  a change  in VNC
>   rather than in FVWM.
>
> I don't see how Fvwm can help.
> Try the VNC folks.

I agree that it looks like the problem is outside fvwm. However,
I expect there are only a few circumstances that can cause
PrintInfo Bindings to not output the default builtin F1
keybinding on fvwm started without configuration. I would have
hoped that the fvwm developers could provide some information
about these circumstances, for instance about presence or absence
of certain X server extensions that can trigger that behavior.

Best regards,

Hendrik
This email and any attachments thereto may contain private, confidential, 
and/or privileged material for the sole use of the intended recipient. Any 
review, copying, or distribution of this email (or any attachments thereto) by 
others is strictly prohibited. If you are not the intended recipient, please 
contact the sender immediately and permanently delete the original and any 
copies of this email and any attachments thereto.

Bug#784328: FVWM: fvwm hotkey problem inside vnc

[Hendrik Tews]

Hi,

[reincluding the fvwm list, because I still have the hope that
our observations might trigger an idea that leads to a solution]

Claude, thanks for restating your FreeBSD observation, I was not
aware of that. From that I conclude that the bug is fixed or
introduced by either

- the Debian or FreeBSD patches

- the different fvwm configurations

- the different libraries

Claude, what did you precisely install on the FreeBSD system, the
port or a fvwm package? If it is the port, could you send the
compilation log? If it is the package, was it fvwm-2.6.5_7?

I am asking, because I want to try to compile a fvwm on Debian that
is identical wrt patches and configuration to your FreeBSD
version.

Bye,

Hendrik
This email and any attachments thereto may contain private, confidential, 
and/or privileged material for the sole use of the intended recipient. Any 
review, copying, or distribution of this email (or any attachments thereto) by 
others is strictly prohibited. If you are not the intended recipient, please 
contact the sender immediately and permanently delete the original and any 
copies of this email and any attachments thereto.

Bug#784328: fvwm hotkey problem inside vnc

[Hendrik Tews]

Dear all,

[sorry for crossposting - but I would like to connect different
sources about this problem]

The problem is that fvwm does not install any keybindings when
started inside a vncserver, see Debian bug #784328 or Raphael's
post "Understanding why Key bindings are not installed" on the
fvwm mailing list on March 2, 2015. I have this problem with fvwm
2.6.5 from Debian stable and vnc4server 4.1.1 and tightvncserver
1.3.9. To reproduce the problem, start vncserver on your local
machine and start fvwm without any configuration inside that vnc
X xerver. Then open the FvwmCommand console and do PrintInfo
bindings there.

The work around that I found is using the tigervncserver, in
there, fvwm installs the key bindings as expected. There are deb
packages of tigervncserver (follow releases -> the binary link on
bintray -> Files). They don't install right away on Debian
stable, but when you unpack them (dpkg -x) and make some
symlinks, you can run run the binaries.

However, for me, tigervnc shows the Ctrl-space problem, i.e.,
Ctrl-space is not transmitted correctly to applications inside
vnc, making it quite difficult to work with emacs inside
tigervnc. I am therefore still interested in a solution to the
fvwm key bindings problem.

If anybody has a idea about how to convince fvwm to install key
bindings inside fvwm, please follow up on this email.

Best regards,

Hendrik Tews


This email and any attachments thereto may contain private, confidential, 
and/or privileged material for the sole use of the intended recipient. Any 
review, copying, or distribution of this email (or any attachments thereto) by 
others is strictly prohibited. If you are not the intended recipient, please 
contact the sender immediately and permanently delete the original and any 
copies of this email and any attachments thereto.

Bug#802166: otags: fails to install: post-installation script returned error exit status 3

[Hendrik Tews]

Mehdi Dogguy  writes:

> Can you give us a hint on how to work out a real fix for this issue?

I am looking at it now. There is quite a bit new syntax in 4.02,
yielding quite a few warnings about incomplete pattern in otags.
Each of these will crash otags in the same way, for instance
attributes, extension nodes, extensible variant types.

I try to make a new release, but it will take more than one day.

Bye,

Hendrik

Bug#802166: otags: fails to install: post-installation script returned error exit status 3

[Hendrik Tews]

Hi,

it's a pattern matching failure in tag_module_type, which means
the file stdLabels.mli contains some module type that I didn't
know about when I wrote tag_module_type.

As a quick solution you can add a catch-all line

   | _ -> ()

to tag_module_type. This will hopefully fix the bug, but you
won't get tags for the offending module type.

If somebody could send me that stdLabels.mli (or include it here
in the bug report) I will try to take a look.

(When I wrote otags, I explicitly avoided catch-all clauses. This
way I could check at compile time that I covered all existing
syntax. You are paying the price for this now - sorry for that.
You may add catch-all clauses to all functions in tags.ml to
avoid crashes like this one for new syntax constructs.)

Bye,

Hendrik

Bug#779597: proofgeneral: Buffer is read-only when there is an error compiling dependant Coq files

[Hendrik Tews]

Ralf Jung p...@ralfj.de writes:

 Weird enough, it shows that error even when there is nothing to do: A

This might be because the buffer is always initialized, see
coq-init-compile-response-buffer.

Looking quickly over the code, all usages of this buffer seem to
be guarded with (inhibit-read-only t), which should disable the
read-only check. I don't know what is going on, I have to look
more carefully.

Bye,

Hendrik


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

Bug#779597: proofgeneral: Buffer is read-only when there is an error compiling dependant Coq files

[Hendrik Tews]

Thanks for reporting this.

I remember having problems with this when I originally wrote the
compilation feature for Coq. IIRC, the problem is that there is
no clear interface for inserting text in write protected buffers.
Probably the hack that I used for this broke in the newest emacs
version. I have to check this.

Bye,

Hendrik


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

Bug#768619: proofgeneral: FTBFS in jessie: build-dependency not installable: emacs23-nox

[Hendrik Tews]

Hi,

thanks, this is certainly one way to solve the bug. I would
however have preferred to fix the problem in sbuild, as Felix
Gruber pointed out. The build-dependencies of the package are
IMHO not wrong, the package should also build with emacs23.

Bye,

Hendrik


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

Bug#746466: proofgeneral hijacks the emacs icon identity

[Hendrik Tews]

 Incidentally, after removing that entry, the ProofGeneral icon does
 still appear in the Application menu even though its not used for

Yes, I believe I also saw this. I attributed this to some caching
and hope that this goes away when we solve the other problem.

Hendrik


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

Bug#766917: debian-maintainers: annual ping for Hendrik Tews

[Hendrik Tews]

Package: debian-maintainers
Severity: normal

Hi,

this is my ping for 2014.

Hendrik


pgpuoj5uEmlHy.pgp
Description: PGP signature

Bug#746466: proofgeneral hijacks the emacs icon identity

[Hendrik Tews]

Hi,

I was able to reproduce the problem with gnome now. BTW, KDE
doesn't have this problem.

The problem is not the emacs lisp code that runs on every emacs
startup (try commenting the load line in
/etc/emacs/site-start.d/50proofgeneral.el!) the problem is the
line 

  StartupWMClass=Emacs

in /usr/share/applications/proofgeneral.desktop . When you
comment this line, the gnome desktop shows the emacs icon for
emacs. However, it will then also show the emacs icon for
proofgeneral. 

As intermediate solution I will comment the WMClass line. But I
will keep this bug open until I find out whether there is a
solution that shows the right icons for both, emacs and
proofgeneral.

Bye,

Hendrik


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

Bug#758968: proofgeneral: called emacs-package-remove as a new-style add-on, but has no compat file.

[Hendrik Tews]

Hi,

thanks for the report and please apologize the delay. I'll add
the necessary emacsen-compat file in the next version of this
package to fix this bug.

Bye,

Hendrik


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

Bug#751049: proofgeneral: FTBFS - pdfetex (file cm-super-t1.enc): cannot open encoding file for reading

[Hendrik Tews]

Hi,

please apologize the delay. I am investigating now.

@Michael Tautschnig: Can I simply close this bug if the package
now builds fine in cowbuilder?

Bye,

Hendrik


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

Bug#746466: proofgeneral hijacks the emacs icon identity

[Hendrik Tews]

Hi,

thanks for your report and please apologize the delay. I agree
with you, the icon should not change when emacs is started as
emacs. However, I don't see the icon change in my window manager
(fvwm). 

What desktop are you using? Does this happen immediately after
starting emacs or only after visiting a Coq file?

Bye,

Hendrik


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

Bug#755526: iceweasel: ntlm authentication not working

[Hendrik Tews]

Package: iceweasel
Version: 30.0-2
Severity: important

Dear Maintainer,

-- Package-specific info:

one of the recent updates broke ntlm authentication for me. About
2 weeks ago, iceweasel always asked for username and password
when I visited a site that requires ntlm authentication. The
current version doesn't ask for credentials, but only shows 401
unauthorized. 

Please restore the old behavior, where iceweasel asks for
credentials or provide some other way, where I can visit ntlm
pages where the only way to get the credentials is that I type
them.

I found out about the ntlm protection with lynx, which told me
that the site is ntlm protected.

chromium version 35.0.1916.153-2 asks for credentials and
displays the site.

I also tried a new iceweasel user profile, it shows the same
problem.

Bye,

Hendrik

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

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

Versions of packages iceweasel depends on:
ii  debianutils   4.4
ii  fontconfig2.11.0-5
ii  libasound21.0.28-1
ii  libatk1.0-0   2.12.0-1
ii  libc6 2.19-7
ii  libcairo2 1.12.16-2
ii  libdbus-1-3   1.8.6-1
ii  libdbus-glib-1-2  0.102-1
ii  libevent-2.0-52.0.21-stable-1
ii  libffi6   3.1-2
ii  libfontconfig12.11.0-5
ii  libfreetype6  2.5.2-1
ii  libgcc1   1:4.9.0-7
ii  libgdk-pixbuf2.0-02.30.7-1
ii  libglib2.0-0  2.40.0-3
ii  libgtk2.0-0   2.24.24-1
ii  libhunspell-1.3-0 1.3.3-2
ii  libnspr4  2:4.10.6-1
ii  libnss3   2:3.16.3-1
ii  libpango-1.0-01.36.3-1
ii  libsqlite3-0  3.8.5-2
ii  libstartup-notification0  0.12-3
ii  libstdc++64.9.0-7
ii  libvpx1   1.3.0-2
ii  libx11-6  2:1.6.2-2
ii  libxext6  2:1.3.2-1
ii  libxrender1   1:0.9.8-1
ii  libxt61:1.1.4-1
ii  procps1:3.3.9-7
ii  zlib1g1:1.2.8.dfsg-1

iceweasel recommends no packages.

Versions of packages iceweasel suggests:
pn  fonts-mathjax  none
ii  fonts-oflb-asana-math  000.907-6
ii  fonts-stix [otf-stix]  1.1.1-1
ii  libcanberra0   0.30-2
ii  libgnomeui-0   2.24.5-3
ii  libgssapi-krb5-2   1.12.1+dfsg-4
pn  mozplugger none

-- no debconf information

Bug#738392: proofgeneral: FTBFS: Latex errors

[Hendrik Tews]

Hi,

Hideki Yamane writes:

   Also, I'll upload it to 10-delayed queue. If you don't want it, please
   tell me.

thanks a lot for helping me out here!

Bye,

Hendrik


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

Bug#728406: debian-maintainers: Please add Hendrik Tews as DM

[Hendrik Tews]

Package: debian-maintainers
Severity: normal

Please add my key to the Debian Maintainers keyring.
The jetring changeset is attached.

Thanks,

Hendrik Tews

-- System Information:
Debian Release: 7.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (x86_64)

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

Comment: Hendrik Tews hend...@askra.de
Date: Thu, 31 Oct 2013 21:55:48 +0100
Action: import
Recommended-By:
  Stéphane Glondu glo...@debian.org, Sylvain Le Gall gil...@debian.org
Agreement:
  http://lists.debian.org/debian-newmaint/2013/10/msg00024.html
Advocates:
  http://lists.debian.org/debian-newmaint/2013/10/msg00027.html
  http://lists.debian.org/debian-newmaint/2013/10/msg00031.html
Data: 
  -BEGIN PGP PUBLIC KEY BLOCK-
  Version: GnuPG v1.4.12 (GNU/Linux)
  
  mQINBE8LCoIBEADkaTTmN3ov84eqUx2ykB2xOifh/7DzjFhRqJACaZg18CcNoBqk
  eiwYMZzQq7Jnd8XpA/hrcyAhMKObVAcBGC7h3MfxM2iefcqS561903V6pSsAERpa
  lVcfkFqXJMzbPdDDwcHNNjyLuYSFBo4SpNfqBDbOt1asH5iz9N+yWdhYQ24taaM6
  iGy2YnTqY9apiN+OI9sGrPRT2TjdQxMl/pdxxTf2rzuk9HlSoARFi8SxrUaxyycM
  Twcy7uW+gRC9A8IFf5Yor4EFGzghy4kuQD82JCJZ+BcsHhxfxnfuVMAhSx8lwSUH
  SJMdXOuNa6Xgcv+Ubd2eqPeEuvDz1tdrBjdG8R1USonSER7OsYS3nHZqXrGGOkft
  SKzCnoUa2powobPsx9+iPN3ioOz3MmO9PzNhGpzjUyoTm7taxByv3xnADQN1glW6
  fgw2GSCEWqrlRVWLbbdy10Qgqa1C/f0vjqYyUDkbiOlyvWoh1ZxXE6jxvXKAVoi2
  vCZJEsTFgvRugO9L40/yux8COXCNbKm4O6xhjURTkw5bwEDBizxb3gRmcIHj8xIc
  NONVrixvCbHr65+4Cj0zgRk4XNrm3g4nu9fXy52tbSm0B5l4uDKnfpGicZBL5uVw
  VWW8ui6uw41wcczC8eXAECy6Am4hJm177bVsk4tBhKJBm978r0JFhl5ipQARAQAB
  tB9IZW5kcmlrIFRld3MgPGhlbmRyaWtAYXNrcmEuZGU+iQI6BBMBCAAkAhsDBQsJ
  CAcDBRUKCQgLBRYCAwEAAh4BAheABQJPCwuIAhkBAAoJEOxoV33tyu5oqtYP/0I3
  X1gaSxkJPQc/p8mHPNgRE1b0Sr91AsRL53XTppA3QKjPJE342Myq5EVAbnCiTVTe
  I1q0Ox1XkXpSRYbMZNEWnuncvTy26roDi7pRumakCxoWraWCJ6gEfEFVP46sbUM9
  5F8nGGAWgDQgrMcdvPqipatWcXYXmc8CqWzc6PYl059JwsONmOZBaQ2LBFgdXqDz
  pztO2W96jYWRYsvrikph30iGzSx/u4uJMCK1Hict7H44Jcd7/jTmAel4m6pVTR7s
  YLmHevVKOcS63+CJcGEN+ZdmDSCAtv6hic15K2/2FMM/v0bvNTp9jaQPBMi7vP7Z
  CRpz48FkhCuooUCimGns1Wamj2J1CZxxW7FbUyVTRTLi3ucrThczly0IqXNNSS9T
  kM8vleu1PAOb6pLkWfUY9oivVodUyJop3QF48sGyj4xwj4kOWLgou/g8l0QxX29p
  4n4eQczD6mUW/8dPQdr1D/iFngVvhmmAswFOr5o7y4NYn3oq7KMjzjES8o6nhlCG
  EHtNKL3hrJEfn+Hyl/goc8tzYM7yjObLS7ojFNAkSgsO5LMej5uMGbwyhKvVVQ+S
  QMFrkWrFjTkX+83a8yK+ruEi/fxRyqt1oShsDoRzL2v4ErCltU62CKWI+z8oD+MX
  AwypyBNUIGWpqRO+muuaJWC2aO6Yv/0h2sBhkjsriQIcBBABAgAGBQJSOt77AAoJ
  EDkUtTL0376ZD0kP/3fj0IC9i155RdtC9/WWCa/47irYo/fVzEZbYOJ+W/0JV3yX
  P8i8OkQLVHhTFvQhf6SJaEXYj1kWAjWpnbvSnnWpUnGk3vfq9qu5knor1u5qCoD2
  BwNx5BrTPDwTKvnV0hNkhv/bODm4B0fiFVzALavK9DvITOXvskwHbLemUQIj5lTg
  iNCDZNwliBsm+jkuh/6Q021vyKQKi6Hd7SPETMcumk6/KB/58OMxo/KPZXpU24rX
  S2PZaDP1KoGYuSraiaGJkgKK/SHeB8EAYO6rjRHBjbMFWnAgS4IGGTpM7SHPYt5+
  ZKx+KdDTJBLyoItC0LJDK9fgooFcqEEQoMzTxWbOBKCsKi/TUWEyxMxHB6OQOz2U
  7lhypF2kHtsNz9Hz6HVuGK829qJba7MJHQTHXNcy3ecmpJcMVdjwvmFOWTzO7Ggl
  dx/W7lPBJkZzmxPyDgveHNrWypRLT4gnwT5neLczym59zRdrM1bw3UqMTPusdsLx
  H781ZMwxnOhUAUOsuuXs9aOZT2rTWaufJtTmFO4ZOjHXm6mBxpSL3OPBJsmDHJga
  R8lb7TQzVpfQ366qKzUPSsc/nzqxX+TzTzQl0ANI+MNZ6x89Flbu+f+pmiD23Xob
  7YXsLT5PJrJlMOCUAz0LtF95YpYCyYqXS1hHt9g/V7dRu+kTq6EH7f1FYLi+iQIc
  BBABCgAGBQJSOiNeAAoJEHhT2k1JiBrTdvAP/08A3j3geh1SFKA380Xis7j4n75J
  06rMMrSq6/EnAUQLRf5YRrxEcRe0QT1EU2GjFawo6gbPkyESy+J1awpy/0t+Z2qf
  5WYhRCMu2KhTMUjvpo+nyaT+UJALFFxQtAWnWNtmm0BdBvOvo/u+eP8DKEuRbCLY
  UOj57KEDOGSbtgrmhiD+HpZUsjr7knBlW76rbehPa+2AmTgdpF024jYfP+QqU9rU
  DSEUFMpdabmN6KVW5YXELQNZbgGy4G7F9orq+jLWESTYLsM5UWccN1rW+ChlD31k
  xGmZ+J6d+qczevttiN4f+9+QIH3Ju+THq7YE9hnGu2Yna2h4Uo76W4Uag+zDLTr7
  5NAJIEaX2XCLHfnR+o0/nrgi23YPermcMFr4wMVkdiAhe2cD/8C0LWvSCaanz00w
  t6NT2g02Vt+uQKMT1MTJPPszD1LkSuOaVuq5qmGMQmCtshpvI0FCs5rdug0STYib
  6UhoUIVIMIUF0ktPOmRFhH29WjJtZnlMq1oJNewuGU/TnS8bgL5jiYvaSYcV6K1X
  QjTrjGkWwa8F2qeIuGrV0Hi5HhdO6hPFjC69RUJPQWspJ4H26HzrM0mJz3rmiJES
  ZahxjDnb00D+0MtCrOzTgZusVl8kDTmFLf64Ttgw1Qm4OdpCW8kadfqYFfY9YhmP
  McJubCho1I23JXPgiEYEEBECAAYFAlJU90YACgkQm0bx+wiPa4wShgCgnabiKVV6
  JEu54QsPavieFQ+NM2oAoI6Ms07PydARlhKOVtUGm6ErNQwsiQIcBBABAgAGBQJS
  VPcfAAoJEEvNBWfCltBdrEgP/iPJT9k404b+m1iAZMk+JmD96iWv075OOUzCnF/B
  t2D6rZGdnA6ZGp1m6zOG9xEm4Y+OwaUjloikgO7YjWJ1+AcU2qQfkjVZGDy8py9c
  wEMEjQLCutecmwrmiEOPLwJqN+zIq9OHQhiK9GTzpq6wxB7RMB22AkUxscOIo1dB
  qXh/pqwflnTnZkdQS9wQdVsCBZwENS5TFLKPcZn86iNhkekuBje5btkoio52soPa
  ydql5AKDdV/PBpk58ZfmK77/ZcJNfYxc5KkoWIDrPC6gvx9OJ9aZLv5F0wyRXAgy
  M/N8W6L6AFuiSIdh+RGP+r+xJQTJNFsjTmB1M3WL+L2Uz9CGcNWE4Za5fLvpeu5W
  8vI7Rwv+cprGaQYD9+nazMJx75jqtM3miZrGtuhSiRJn8Rj8D5zCZXLcYs2xXc1q
  Y0nvo8lBX2p/HzNAxUkwe8HO5f02jninUldkqGVU9VY09/UZVklpnw9YVpK/vnk/
  qcurWOKBZbU3YP/jIzOm3wWcvicp0ab39Qbeer+N9HC4aIgd3JHBDT0Ee+9BCqJH
  +vvvrE3cBuZBmlSNqsImFUfjBJdRT+IHJsy0hDa2xKlrKwS3SmIK+x2OmWPGq5W7
  jhKnYA7cdX4Km2pacaiXv8lF7dKcQRlJ5yNfYbsj3vdqIyeyyg0XQsegCdGT2rha
  dKwatChIZW5kcmlrIFRld3MgPHRld3NAb3MuaW5mLnR1LWRyZXNkZW4uZGU+iQI3
  BBMBCAAhBQJPCwtMAhsDBQsJCAcDBRUKCQgLBRYCAwEAAh4BAheAAAoJEOxoV33t

Bug#718748: oasis: FTBFS on armhf

[Hendrik Tews]

forwarded 718748 
https://forge.ocamlcore.org/tracker/index.php?func=detailaid=1306group_id=54atid=291
tags 718748 confirmed upstream
thanks


Hi,

Hector Oron zu...@debian.org writes:

 Your package fails to build from source on Debian autobuilder network.

Thanks for recording this issue with the BTS. The software itself
builds fine, the problem is that the tests expect wrong results
on bytecode architectures. I discussed this with upstream already
in June, Sylvain works on it, but I haven't got a patch yet.

Note that there is no real difference between oasis 0.3.0-1 and
0.3.0-2, it's only that the tests are disabled in 0.3.0-1.

Please tell me if this build failure is a real problem for you,
because I'll then prepare 0.3.0-3 with tests disabled again.

Bye,

Hendrik


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

Bug#716728: E: Invalid_argument(String.create)

[Hendrik Tews]

forwarded 716728 
https://forge.ocamlcore.org/tracker/index.php?func=detailaid=1295group_id=54atid=291
thanks

upstream plans to fix this issue in version 0.4.

Bye,

Hendrik


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

Bug#138157: Does a workaround exist?

[Hendrik Tews]

Johannes Schauer j.scha...@email.de writes:

   Does there exist a workaround for it? For example I have to use the IEEEtran
   class [1] but can't view the dvi because of this bug:

The advi FAQ at http://advi.inria.fr/faq.html says

How to visualize Adobe PostScript fonts like ptmr8t using Active-DVI ?

Answer: You have to preprocess the file with the command
dvicopy which expands virtual fonts. For instance:

dvicopy foo.dvi foo.advi  advi foo.advi

usually works fine. 

Does this work for you?

Bye,

Hendrik


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

Bug#596622: libextlib-ocaml-dev: New upstream version

[Hendrik Tews]

Hi,

extlib 1.5.2-1 does not compile with OCaml 4.00 (because of the
changes in the hashtbl signature). Upstream has fixed this in
version 1.5.3. 

Bye,

Hendrik


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

Bug#711524: atdgen: fails to build with new ocaml-atd

[Hendrik Tews]

Colin Watson cjwat...@ubuntu.com writes:

   Package: atdgen
   Version: 1.2.2-1
   Severity: serious
   User: ubuntu-de...@lists.ubuntu.com
   Usertags: origin-ubuntu saucy

   I tried to rebuild atdgen against the new ocaml-atd, and it failed as
   follows:

The current upstream version of atdgen is 1.2.5, it build-depends
on biniou and yojson, whose packages are both not up-to-date in
Debian, too.

Why do you expect that an old atdgen compiles with an up-to-date
version of ocaml-atd? I don't think this is a bug at all.

I am working on updating all these atd related packages from
Martin Jambon. The problem is that all the still missing ones
build-depend on biniou and biniou has one test that fails on i386
(and works on amd64). So far, Martin only confirmed that this
test is supposed to work, but I haven't got a fix yet.

Bye,

Hendrik


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

Bug#711296: ftp.debian.org: override: hol-light:math/extra

[Hendrik Tews]

Package: ftp.debian.org
Severity: normal

hol-light depends on camlp5 and camlp5 is ocaml/extra.

Hendrik


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

Bug#672480: prooftree: fixing owner

[Hendrik Tews]

owner 672480 !
thanks

Repeating myself: The packaging effort is almost finished: A new
up-to-date version is waiting in the OCaml maintainers git repo
for review and sponsoring, see
http://anonscm.debian.org/gitweb/?p=pkg-ocaml-maint/packages/prooftree.git
and
https://lists.debian.org/debian-ocaml-maint/2013/05/msg00194.html

Bye,

Hendrik


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

Bug#687977: proofgeneral-doc: Info page refers to missing file

[Hendrik Tews]

Hi,

I looked again at your bug report. 

With the info tutorial you mean section 2.1 Walkthrough
example in Isabelle in the Proof General user's manual packaged
in proofgeneral-doc?

I just noticed that the upstream sources contain an example file,
that is not included in the packages. My plan is now to install
this example file as /usr/share/doc/proofgeneral/coq_example.v
and put a hint on this location into section 2.1. 

Bye,

Hendrik


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

Bug#707331: proofgeneral: incompatible with new Coq 8.4 features

[Hendrik Tews]

   this. Could you please update proofgeneral to that version?
   
Yes, it's on my todo list.

Hendrik


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

Bug#679917: Lowering bug severity

[Hendrik Tews]

severity 679917 grave
thanks
   
I'am sorry, but the described workaround does not work. I am
therefore raising the severity again.

Today with korganizer 4:4.4.11.1+l10n-3+b1 and systemsettings
4:4.8.4-6 and the attached file in my home directory
(/home/tews):

I first start systemsettings and go personal information -
calendar - add. I put a.ics as Name and /home/tews as
Location. I do OK, Apply and quit systemsettings. When I start
korganizer now, it has a.ics in the list of calendars, but shows
the error Error while loading a.ics.

The same happens, when I use a as Name in systemsettings.

Note that I can open a.ics fine in a separate window.

Bye,

Hendrik



a.ics
Description: Binary data

Bug#679917: Lowering bug severity

[Hendrik Tews]

severity 679917 important
thanks


I just noticed that the workaround works if I store the calendar
file, or place symlinks, in ~/.kde/share/apps/korganizer.

I would really appreciate if somebody could explain this weird
behavior... 

I don't think raising the severity in my previous message worked,
but now I am lowering again to important. 

Bye,

Hendrik


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

Bug#704207: linux-image-3.2.0-4-686-pae: soft lockup after suspend to disk

[Hendrik Tews]

Package: src:linux
Version: 3.2.39-2
Severity: important

Dear Maintainer,

-- Package-specific info:
** Version:
Linux version 3.2.0-4-686-pae (debian-ker...@lists.debian.org) (gcc version 
4.6.3 (Debian 4.6.3-15) ) #1 SMP Debian 3.2.39-2

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-686-pae 
root=UUID=b2ab74ed-fc01-4d81-99d1-bcad9228433b ro splash acpi_osi=Linux 
acpi_backlight=vendor quiet

** Not tainted

** Kernel log:
[   47.162902] cfg80211: (549 KHz - 571 KHz @ 4 KHz), (N/A, 
2700 mBm)
[   58.018904] wlan0: no IPv6 routers present
[  209.505682] PM: Marking nosave pages: 0009c000 - 0010
[  209.505686] PM: Basic memory bitmaps created
[  209.700702] Syncing filesystems ... done.
[  209.701573] Freezing user space processes ... (elapsed 0.01 seconds) done.
[  209.714781] PM: Preallocating image memory... done (allocated 154381 pages)
[  209.847941] PM: Allocated 617524 kbytes in 0.13 seconds (4750.18 MB/s)
[  209.847943] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) 
done.
[  209.862545] Suspending console(s) (use no_console_suspend to debug)
[  209.872483] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[  210.401574] PM: freeze of devices complete after 539.922 msecs
[  210.401870] PM: late freeze of devices complete after 0.292 msecs
[  210.402322] ACPI: Preparing to enter system sleep state S4
[  210.544772] PM: Saving platform NVS memory
[  210.545563] Disabling non-boot CPUs ...
[  210.649049] CPU 1 is now offline
[  210.752838] CPU 2 is now offline
[  210.856658] CPU 3 is now offline
[  210.857081] Extended CMOS year: 2000
[  210.857156] PM: Creating hibernation image:
[  210.958915] PM: Need to copy 153414 pages
[  210.958918] PM: Normal pages needed: 45812 + 1024, available pages: 181795
[  210.857188] PM: Restoring platform NVS memory
[  210.857723] Extended CMOS year: 2000
[  210.857769] Enabling non-boot CPUs ...
[  210.857911] Booting Node 0 Processor 1 APIC 0x4
[  210.857912] smpboot cpu 1: start_ip = 98000
[  210.868100] Initializing CPU#1
[  210.868919] Calibrating delay loop (skipped) already calibrated this CPU
[  210.889391] NMI watchdog enabled, takes one hw-pmu counter.
[  210.890127] CPU1 is up
[  210.890647] Booting Node 0 Processor 2 APIC 0x1
[  210.890654] smpboot cpu 2: start_ip = 98000
[  210.900840] Initializing CPU#2
[  210.901670] Calibrating delay loop (skipped) already calibrated this CPU
[  210.922339] NMI watchdog enabled, takes one hw-pmu counter.
[  210.922818] CPU2 is up
[  210.923189] Booting Node 0 Processor 3 APIC 0x5
[  210.923193] smpboot cpu 3: start_ip = 98000
[  210.92] Initializing CPU#3
[  210.934201] Calibrating delay loop (skipped) already calibrated this CPU
[  210.954775] NMI watchdog enabled, takes one hw-pmu counter.
[  210.955302] CPU3 is up
[  210.958171] ACPI: Waking up from system sleep state S4
[  211.321285] PM: early restore of devices complete after 0.632 msecs
[  211.361809] i915 :00:02.0: setting latency timer to 64
[  211.361813] ehci_hcd :00:1a.0: setting latency timer to 64
[  211.361828] snd_hda_intel :00:1b.0: setting latency timer to 64
[  211.361837] usb usb1: root hub lost power or was reset
[  211.365785] ehci_hcd :00:1a.0: cache line size of 64 is not supported
[  211.365796] snd_hda_intel :00:1b.0: irq 42 for MSI/MSI-X
[  211.365799] ehci_hcd :00:1d.0: setting latency timer to 64
[  211.365812] usb usb2: root hub lost power or was reset
[  211.369782] ehci_hcd :00:1d.0: cache line size of 64 is not supported
[  211.369806] pci :00:1e.0: setting latency timer to 64
[  211.369817] ahci :00:1f.2: setting latency timer to 64
[  211.382878] sd 0:0:0:0: [sda] Starting disk
[  211.687845] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[  211.695835] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[  211.698494] ata5.00: configured for UDMA/100
[  211.715829] usb 1-1: reset high-speed USB device number 2 using ehci_hcd
[  211.739714] ata1.00: configured for UDMA/100
[  211.959399] usb 2-1: reset high-speed USB device number 2 using ehci_hcd
[  212.126556] wlan0: deauthenticated from 00:24:01:21:02:e6 (Reason: 6)
[  212.150154] cfg80211: Calling CRDA to update world regulatory domain
[  212.378774] usb 2-1.5: reset high-speed USB device number 3 using ehci_hcd
[  212.727334] PM: restore of devices complete after 1367.984 msecs
[  212.747957] Restarting kernel threads ... done.
[  212.748111] snapshot_ioctl: ioctl '4004330c' is deprecated and will be 
removed soon, update your suspend-to-disk utilities
[  212.748113] Restarting tasks ... done.
[  212.760045] cfg80211: World regulatory domain updated:
[  212.760048] cfg80211: (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
[  212.760052] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[  212.760055] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[  212.760058] cfg80211: (2474000 KHz - 2494000 KHz @ 

Bug#696408: flashplugin-nonfree: epiphany and iceweasel crash

[Hendrik Tews]

Hi,

I would also like to suggest that the install script checks for
SSE2 and installs an older version, if SSE2 is not present. For
me 11.1.102.63 seems to work.

Could somebody explain me, severity 'normal'? The problem makes
the package unusable, it even makes iceweasel break, so it should
have grave or critical.

Bye,

Hendrik


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

Bug#702349: lintian should not complain about hardening for package written in pure Ocaml

[Hendrik Tews]

Prach Pongpanich prach...@gmail.com writes:

   lintian should not complain about hardening for package written in
   pure Ocaml [0],[1],[2]

The problem is, that even pure OCaml contains enough features
that may permit arbitrary memory corruptions by an attacker. For
instance, String.unsafe_blit has no bounds checks, Obj.magic is
an unsafe cast, Marshal.from_channel may break the type
system, ...

Moreover, it is almost impossible to avoid these unsafe
functions, because they are used in the standard library. 

In principle I agree, that programs written in a certain subset
of OCaml do not need these hardening features. However, at the
moment this safe subset is not even identified...

Bye,

Hendrik


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

Bug#702349: lintian should not complain about hardening for package written in pure Ocaml

[Hendrik Tews]

   
   OCaml has a built-in notion of unsafe feature (see ocamlobjinfo
   output) that could serve as a starting point for that.
   
Yes, I tried this on 

let f b =
  let a = abcde in
  let c = Obj.magic b in
  String.unsafe_blit c 0 a 0 5

For the .cmo, ocamlobjinfo surprisingly reports

   Uses unsafe features: no

and for the .cmx it doesn't say anything about unsafe features.

Bye,

Hendrik


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

Bug#645079: Bug#: 645079: RFA: coinor-csdp -- A software package for semidefinite programming

[Hendrik Tews]

Hi,

could you provide some more information for potential adopters?

With due to non-GPL compatible licensing you refer to the CPL,
I suppose. Could you elaborate on why the CPL is an issue?

The last upstream release was in April 2010, the upstream bug
tracker has 5 tickets in total, the last dating from 2009. This
looks like upstream development is not really active any more.
Could you tell your opinion on the activity of the upstream
maintainer?

Bye,

Hendrik


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

Bug#695249: unblock: proofgeneral/4.2~pre120605-2

[Hendrik Tews]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package proofgeneral

the new version fixes RC bug #694285 and corrects some wrong
information in README.Debian.

 debdiff ===
diff -Nru proofgeneral-4.2~pre120605/debian/changelog 
proofgeneral-4.2~pre120605/debian/changelog
--- proofgeneral-4.2~pre120605/debian/changelog 2012-06-06 23:17:53.0 
+0200
+++ proofgeneral-4.2~pre120605/debian/changelog 2012-12-04 14:51:47.0 
+0100
@@ -1,3 +1,10 @@
+proofgeneral (4.2~pre120605-2) unstable; urgency=low
+
+  * add Breaks and Replaces dependencies for proofgeneral-doc (Closes: #694285)
+  * delete wrong info in README.Debian
+
+ -- Hendrik Tews hend...@askra.de  Tue, 04 Dec 2012 14:50:27 +0100
+
 proofgeneral (4.2~pre120605-1) unstable; urgency=low
 
   * New upstream release (Closes: #669318)
diff -Nru proofgeneral-4.2~pre120605/debian/control 
proofgeneral-4.2~pre120605/debian/control
--- proofgeneral-4.2~pre120605/debian/control   2012-06-05 23:53:53.0 
+0200
+++ proofgeneral-4.2~pre120605/debian/control   2012-12-04 12:43:31.0 
+0100
@@ -25,6 +25,8 @@
 Section: doc
 Architecture: all
 Depends: ${misc:Depends}
+Breaks: proofgeneral ( 4)
+Replaces: proofgeneral ( 4)
 Recommends: info-browser | pdf-viewer | www-browser
 Suggests: proofgeneral
 Description: generic frontend for proof assistants - documentation
diff -Nru proofgeneral-4.2~pre120605/debian/README.Debian 
proofgeneral-4.2~pre120605/debian/README.Debian
--- proofgeneral-4.2~pre120605/debian/README.Debian 2012-06-06 
13:46:58.0 +0200
+++ proofgeneral-4.2~pre120605/debian/README.Debian 2012-12-04 
14:44:47.0 +0100
@@ -19,27 +19,11 @@
 in the Debian package, please file a bug report against proofgeneral.
 
 
-This Debian package of Proof General does not work with a manual
-installation of Coq. The reason is that Coq installs a file coq.el
-which is loaded when Proof General attempts to load its version of
-coq.el. There are two possible fixes:
-
-1) delete at least coq.el, coq-db.el and coq-syntax.el from the Coq
-   installation, or
-
-2) put 
-
- (add-to-list 'load-path /usr/share/emacs23/site-lisp/proofgeneral/coq/)
-
-   in your .emacs file.
-
-
 This version of ProofGeneral contains support for Prooftree. However,
 because neither Coq = 8.4beta nor Prooftree are in this version of
 Debian, Prooftree support is statically disabled. You can try to use
 Prooftree with this version of ProofGeneral. To do so
 - manually install Coq = 8.4beta
-- apply one of the fixes from the preceding paragraph
 - manually install Prooftree (see http://askra.de/software/prooftree/)
 - restart ProofGeneral
 
@@ -53,4 +37,4 @@
 General website (or by downloading the sources).
 
 
- -- Hendrik Tews hend...@askra.de, Wed,  6 Jun 2012 13:46:26 +0200
+ -- Hendrik Tews hend...@askra.de, Tue,  4 Dec 2012 14:44:47 +0100
 end debdiff ===

unblock proofgeneral/4.2~pre120605-2

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

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


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

Bug#694285: proofgeneral-doc: missing Breaks+Replaces: proofgeneral ( 4)

[Hendrik Tews]

Hi,

thanks for detecting this problem.

 Package:  proofgeneral-doc
 Breaks:   proofgeneral ( 4)
 Replaces: proofgeneral ( 4)
   
It makes certainly sense to add these dependencies, although,
without having read the documentation, I would only add the
Breaks, because the new proofgeneral-doc does not replace the old
proofgeneral. 

I am on a conference next week and I am not a DD, so it might
probably take two weeks until this is fixed. If anybody wants to
do a NMU for this, I would certainly be grateful.

Bye,

Hendrik


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

Bug#693033: Applying options to sub-hierarchies only

[Hendrik Tews]

Hi,

your request is a feature wish and the unison manual says:

   Feature requests are welcome, but will probably just be added to
   the ever-growing todo list. They should also be sent to
   unison-us...@yahoogroups.com.

The standard procedure would be that we forward your request to
unison-us...@yahoogroups.com, it will be added to TODO.txt and,
very likely, nothing else will happen.

It might make more sense if you post your problem yourself to
unison-us...@yahoogroups.com and ask for a workaround there. You
could, for instance, synchronize with 2 unison invocations, where
the first one uses perms = 0 and is restricted to the samba
directories. 

Bye,

Hendrik


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

Bug#679917: korganizer: cannot add ics calendar files

[Hendrik Tews]

   
   Those two errors come from Phonon and more precisely phonon-backend-vlc. Do 
   you have audio working?
   
Yes, audio is working fine. 

   Maybe it would help if you shared the non-working ics file.
   
Have you tried with any ics file? For me korganizer fails for
_every_ ics file. For instance also for the one appended below.


Bye,

Hendrik



a.ics
Description: Binary data

Bug#687977: proofgeneral-doc: Info page refers to missing file

[Hendrik Tews]

   
   the isar/Example.thy (or an equivalent Example.v) file does not exist.
   
I am sorry for the inconvenience, but this is not really under my
control. Isabelle is not available as Debian package and the
Isabelle maintainers distribute Isabelle with their own version
of Proof General. Consequently, I removed all Isabelle stuff from
the Debian Proof General package. If you want to do the Proof
General tutorial with Isabelle, just deinstall the Debian Proof
General package and use the instance that comes with Isabelle.

Alternatively, you can download an example file from the Coq
website and use that for the tutorial.


Bye,

Hendrik


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

Bug#680494: Typo in package description

[Hendrik Tews]

Thanks for the hint. I'll fix this with the next upload.

Bye,

Hendrik



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

Bug#679917: korganizer: cannot add ics calendar files

[Hendrik Tews]

Package: korganizer
Version: 4:4.4.11.1+l10n-3
Severity: grave

Dear Maintainer,

after upgrading from Squeeze to Wheezy I cannot use my old
calendar files any more. 

When I start korganizer, the list of calendars is empty. When I
then select an ics file via File - Import - Import Calendar and
tick Add as new calendar I get the error 

  Unable to create calendar '/home/tews/SharedConfig/calendar.ics'.

and the terminal contains 

[0x8f95d90] main services discovery error: no suitable services discovery 
module
[0x8e507c0] main input error: ES_OUT_RESET_PCR called


When I add the + at the calendar list and put calendar or
calendar.ics as Name, I get Unable to create calendar and
when I acknowledge the error, korganizer dies with a segmentation
fault.



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

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

Versions of packages korganizer depends on:
ii  kde-runtime   4:4.8.4-1
ii  kdepim-runtime4:4.4.11.1-4
ii  libakonadi-contact4   4:4.8.4-1
ii  libc6 2.13-33
ii  libkabc4  4:4.8.4-1
ii  libkcal4  4:4.8.4-1
ii  libkcmutils4  4:4.8.3-2
ii  libkde3support4   4:4.8.3-2
ii  libkdecore5   4:4.8.3-2
ii  libkdepim44:4.4.11.1+l10n-3
ii  libkdeui5 4:4.8.3-2
ii  libkholidays4 4:4.8.4-1
ii  libkio5   4:4.8.3-2
ii  libkmime4 4:4.8.4-1
ii  libknewstuff2-4   4:4.8.3-2
ii  libkontactinterface4  4:4.8.4-1
ii  libkparts44:4.8.3-2
ii  libkpimidentities44:4.8.4-1
ii  libkpimutils4 4:4.8.4-1
ii  libkprintutils4   4:4.8.3-2
ii  libkresources44:4.8.4-1
ii  libphonon44:4.6.0.0-2
ii  libqt4-dbus   4:4.8.2-1
ii  libqt4-qt3support 4:4.8.2-1
ii  libqt4-xml4:4.8.2-1
ii  libqtcore44:4.8.2-1
ii  libqtgui4 4:4.8.2-1
ii  libstdc++64.7.0-8
ii  perl  5.14.2-12
ii  phonon4:4.6.0.0-2
ii  zlib1g1:1.2.7.dfsg-13

korganizer recommends no packages.

Versions of packages korganizer suggests:
pn  kdepim-groupware   none
pn  kdepim-kresources  none

-- no debconf information


Bye,

Hendrik Tews



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

Bug#677666: pbuilder: using BUILDUSERNAME does not change USER

[Hendrik Tews]

Package: pbuilder
Version: 0.211
Severity: important

Hi,

when I use BUILDUSERNAME=pbuilder, pbuilder changes to user
pbuilder, but does not change the value of USER. This yields a
build failure for packages that check via $USER that they are not
configured as root, for example ocaml-cry (#670733).

When I place id and env into the configure script of ocaml-cry at
line 2870, I see

+ id
uid=56789(pbuilder) gid=56789(pbuilder) 
groups=56789(pbuilder),1234(pbuilderccache)
+ env
USER=root
SUDO_USER=tews
USERNAME=root

shortly later the configure script fails, because it must not run
as root.


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

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

Versions of packages pbuilder depends on:
ii  coreutils  8.13-3.2
ii  debconf [debconf-2.0]  1.5.43
ii  debianutils4.3.1
ii  debootstrap1.0.40
ii  dpkg-dev   1.16.3
ii  wget   1.13.4-3

Versions of packages pbuilder recommends:
ii  devscripts  2.11.8
ii  fakeroot1.18.3-1
ii  sudo1.8.3p2-1.1

Versions of packages pbuilder suggests:
pn  cowdancer 0.70
pn  gdebi-core0.8.5
pn  pbuilder-uml  none

-- debconf information:
  pbuilder/mirrorsite: http://ftp.de.debian.org/debian/
  pbuilder/nomirror:
  pbuilder/rewrite: false



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

Bug#670733: Some remarks

[Hendrik Tews]

Mehdi Dogguy me...@dogguy.org writes:

   As such, I'm lowering the severity of these bugs to important.

There is still the question, how to solve all these Incorrectly
thinks it's building as root bugs. From the arguments in this
thread I conclude that the error is in pbuilder's handling of
$USER and that we are not going to patch the affected packages.

If nobody objects I am going to file a bug report for pbuilder
with severity important and block on it.

Bye,

Hendrik



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

Bug#676424: emacsen-common: debian-startup puts items before /usr/local directories in load-path, violating policy

[Hendrik Tews]

   order would be right anyway if the coq package uses
   debian-pkg-add-load-path-item -- which it ought to do anyway.
   
This is wrong. Just read #676424. 

Bye,

Hendrik



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

Bug#670733: Some remarks

[Hendrik Tews]

Romain Beauxis romain.beau...@gmail.com writes:

   I agree that the configure test is naive, but it relies on reasonable
   and documented behaviours and variables.

OK. What is your source of documentation for the contents of
$USER? 

Bye,

Hendrik



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

Bug#513048: using debian-pkg-add-load-path-item may break your package

[Hendrik Tews]

Hi,

the following points might be useful to know when you try to fix
your debian-pkg-add-load-path-item bug:

- the load-path management of emacs wrt to
  debian-pkg-add-load-path-item is broken, therefore items may
  end up before /usr/local items even though you use
  debian-pkg-add-load-path-item

- if you rely on some order in the load-path, then your package
  may break when you switch to debian-pkg-add-load-path-item

See #676424 for more details.

I wasted several hours, because I experienced both problems when
trying to solve my debian-pkg-add-load-path-item bug. At least
Kevin Ryde knows that debian-pkg-add-load-path-item may not work.
I don't understand why he files bug reports without including all
relevant information.

Bye,

Hendrik Tews



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

Bug#676424: emacsen-common: debian-startup puts items before /usr/local directories in load-path, violating policy

[Hendrik Tews]

Package: emacsen-common
Version: 2.0.3
Severity: serious

Hi,

the line

(setq load-path (append add-on-package-paths old-load-path))

in debian-run-directories in debian-startup.el puts directories
which packages have been added to load-path with
debian-pkg-add-load-path-item at the head of load-path, _before_
the /usr/local entries in load-path. This makes the requirement
in the Debian Emacs policy

   Emacs add-on packages may not modify load-path directly.  They must
   use (debian-pkg-add-load-path-item path).  This function will
   make sure that their additions end up in the right place -- before
   the emacs system directories, but after the /usr/local/
   directories.

an absurdity.

Even worse, packages that work fine may break when they switch to
use debian-pkg-add-load-path-item, because the order in the
load-path is wrong. 

For an example, consider coq and proofgeneral and assume both
packages solely use debian-pkg-add-load-path-item (which is not
the case right now). coq installs 50coq.el, which adds
/usr/share/emacs23/site-lisp/coq to load-path. The reorder bug in
debian-startup actually causes a (non-fatal) problem during
proofgeneral installation, which I am not going to explain here.
When proofgeneral is installed it installs 50proofgeneral.el,
which adds site-lisp/proofgeneral/{generic,lib} to load-path.

When you now start emacs you see all these directories at the
head of load-path, before /usr/local items. When you now open a
coq file, say x.v, Proof General loads its Coq incarnation and
adds site-lisp/proofgeneral/coq to load-path. This will now be
added after /usr/local items and appear far after site-lisp/coq.
(require 'coq) therefore loads site-lisp/coq/coq.el instead of
site-lisp/proofgeneral/coq/coq.el and Proof General is completely
broken.

(Yes, Coq and Proof General should not use the same Emacs feature
name for different packages. I am trying to solve this upstream,
see http://lists.inf.ed.ac.uk/pipermail/proofgeneral-devel/2012/000241.html)

Kevin, you filed quite a lot reports about
debian-pkg-add-load-path-item. Would you add a note to all of
them, telling the maintainers that their package may break when
they switch to debian-pkg-add-load-path-item? It took me several
hours to track down this issue, maybe you can one of them save
the hassle.

Bye,

Hendrik Tews


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

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

-- no debconf information



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

Bug#670339: proofgeneral: debian-pkg-add-load-path-item

[Hendrik Tews]

block 670339 by 676424
thanks

Switching to debian-pkg-add-load-path-item breaks Proof General,
see #676424.

Hendrik



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

Bug#670733: ocaml-cry: FTBFS: Incorrectly thinks it's building as root

[Hendrik Tews]

Mehdi Dogguy me...@dogguy.org writes:

   On 13/05/12 23:37, Hendrik Tews wrote:
   
... the incorrect root test comes from file m4/base_checks.m4
   
deleting the line 'RUNNING_USER=$USER' there and running
./bootstrap then yields
   
checking that calling user is not root... ok
   
and the package builds fine (done with autoconf 2.69; maybe its
better to downgrade to 2.68 to keep the patch small).
   

   Thanks for the investigation! Could you prepare patches for the affected

I can commit fixes to the git repositories if I can downgrade to
autoconf 2.68.

However, environ(7) says:

   USER   The name of the logged-in user (used by  some  BSD-derived  pro‐
  grams).

Therefore, I would say pbuilder is wrong with leaving $USER=root.
On the other hand, I cannot find any standard document specifying
$USER on the web,
http://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap08.html
lists $USER, but does not say anything about its contents.


Bye,

Hendrik



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

Bug#672480: first version of prooftree in git

[Hendrik Tews]

Hi,

the DOM git repository contains the first version of the
prooftree package, see
http://git.debian.org/?p=pkg-ocaml-maint/packages/prooftree.git


Comments are welcome. I would of course be happy if I could find
a sponsor for prooftree.

Bye,

Hendrik



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

Bug#672666: Bug#6726XX: ocaml-xxx: FTBFS: Incorrectly thinks it's building as root

[Hendrik Tews]

See #670733 for the source of the problem.

Bye,

Hendrik



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

Bug#672669: ocaml-lame: FTBFS: Incorrectly thinks it's building as root

[Hendrik Tews]

I cannot reproduce the Incorrectly thinks it's building as root
problem. When I try the build fails with

checking for suffix of object files... configure: error: in 
`/tmp/buildd/ocaml-lame-0.3.0':
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details
make: *** [debian/stamp-autotools] Error 1

Bye,

Hendrik



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

Bug#672480: ITP: prooftree -- proof tree visualization for Proof General

[Hendrik Tews]

Andreas Tille writes:
   
   this seems like a perfect target for Debian Science.  Would you consider
   team maintenance.
   
I definitely need a sponsor for the prooftree package. I would
first try with the OCaml task force, because prooftree is written
in OCaml and I have a few other packages that are sponsored
there.

Bye,

Hendrik



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

Bug#672480: ITP: prooftree -- proof tree visualization for Proof General

[Hendrik Tews]

   and tell us, in what task your package might fit best.
   
If prooftree ever makes it into Debian, it should be together
with coq and proof-general, ie. science-mathematics.

BTW:
- matita, agda, prover9 are proof assistants similar to coq, but
  not listed in science-mathematics
- hol-light, currently waiting in the new-queue, too
- minisat would also belong to this group
- you might want to have a separate meta-package
  theorem-proving or formal-methods for all these tools


Bye,

Hendrik



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

Bug#672669: ocaml-lame: FTBFS: Incorrectly thinks it's building as root

[Hendrik Tews]

Hi,

Daniel, are you sure it was ocaml-lame that FTBFS? Here it builds
fine with user id 56789 inside pbuilder.

My previously reported build failure comes from an incorrect
pbuilder setup. The problem was that CCACHE_DIR
(/var/cache/pbuilder/ccache outside and inside pbuilder) was not
writable by BUILDUSERNAME. When I add the necessary permissions,
the package builds fine.

Bye,

Hendrik



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

Bug#670733: ocaml-cry: FTBFS: Incorrectly thinks it's building as root

[Hendrik Tews]

Hi,

I played a bit around to investigate the problem. What I see is:

- inside pbuilder, after installing the build dependencies and
  after patching the sources, dh_clean runs as root
  [env says $SUDO_USER=tews and $USER=root; id says uid=0(root)
  gid=0(root)]

- Later the configure script of the package runs not as root. At
  line 2871 in configure, where the root test is, id says 

uid=56789(pbuilder) gid=56789(pbuilder) groups=56789(pbuilder)

  however, env still says $SUDO_USER=tews and $USER=root. The
  configure script runs `whoami` only if $USER is empty.
  Therefore configure believes $USER=root and aborts.

For me this looks like pbuilder is not setting the environment
correctly when changing to the non-root user. Or the configure
script is wrong in taken the contents of $USER.

Gruss,

Hendrik

PS. To reproduce
- pbuilder create
- pbuilder login --save-after-login
- in the pbuilder shell: useradd -m -u 56789 pbuilder
- put BUILDUSERNAME=pbuilder into /etc/pbuilderrc
- build package with git-buildpackage --git-builder=pdebuild



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

Bug#670733: ocaml-cry: FTBFS: Incorrectly thinks it's building as root

[Hendrik Tews]

... the incorrect root test comes from file m4/base_checks.m4

deleting the line 'RUNNING_USER=$USER' there and running
./bootstrap then yields 

  checking that calling user is not root... ok

and the package builds fine (done with autoconf 2.69; maybe its
better to downgrade to 2.68 to keep the patch small).

Bye,

Hendrik



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

Bug#671676: emacsen-common: sample install file does not work properly

[Hendrik Tews]

Hi,

if I understand correctly, the -f flag is needed, because during
update the install file is run without the remove file.

But in this case the install file should better delete all files
from the elc directory. Otherwise it will leave dangling symlinks
and outdated elc files behind, if the upgrade version has fewer
el files.

Bye,

Hendrik



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

Bug#672476: emacsen-common: use debian-pkg-add-load-path-item in install file?

[Hendrik Tews]

Package: emacsen-common
Version: 1.4.22
Severity: wishlist

Hi,

debian-emacs-policy mandates debian-pkg-add-load-path-item in
section 9. Many packages change the load-path in their
emacsen-install script for compilation.

I would suggest to make it explicit in the policy whether
debian-pkg-add-load-path-item is also required in these install
scripts. If it is, the dependency on emacsen-common must actually
be a Pre-Depends.


-- System Information:
Debian Release: 6.0.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (x86_64)

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

Versions of packages emacsen-common depends on:
ii  bsdmainutils  8.0.13 collection of more utilities from 

emacsen-common recommends no packages.

emacsen-common suggests no packages.

-- no debconf information

Bye,

Hendrik



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

Bug#672478: dh-make: emacsen-install.ex template violates Debian emacs policy

[Hendrik Tews]

Package: dh-make
Version: 0.60
Severity: normal

The debian emacs policy states in section 9 that
debian-pkg-add-load-path-item must be used to manipulate
load-path.

Therefore the template should do contain

cat  EOF  path.el
(debian-pkg-add-load-path-item .)
(setq byte-compile-warnings nil)
EOF



-- System Information:
Debian Release: 6.0.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (x86_64)

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

Versions of packages dh-make depends on:
ii  debhelper 9.20120419~bpo60+1 helper programs for debian/rules
ii  dpkg-dev  1.15.8.12  Debian package development tools
ii  make  3.81-8 An utility for Directing compilati
ii  perl  5.10.1-17squeeze3  Larry Wall's Practical Extraction 

dh-make recommends no packages.

Versions of packages dh-make suggests:
ii  build-essential   11.5   Informational list of build-essent

-- no debconf information


Bye,

Hendrik



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