Bug#1055792: colcon: Files under install/lib/ are missing

2023-11-11 Thread Yasushi SHOJI
Package: colcon
Version: 0.15.0-2
Severity: normal
X-Debbugs-Cc: none, Yasushi SHOJI 

Dear Maintainer,

First of all, thank you for fixing #1055537.

Today I found another issue with 0.15.0-2.

I just built joint_state_publisher with 0.15.0-2 and got the following
error:

[ERROR] [launch]: Caught exception in launch (see debug for traceback):
package 'joint_state_publisher_gui' found at
'/home/yashi/work/yoshida/avatar-ws/install', but libexec directory
'/home/yashi/work/yoshida/avatar-ws/install/lib/joint_state_publisher_gui'
does not exist

So I took a diff of all files installed by joint_state_publisher using
0.12.0 and 0.15.0-2, and here is the outcome:

❯ diff -u /tmp/colcon-0.12.log /tmp/colcon-0.15.log
--- /tmp/colcon-0.12.log 2023-11-12 00:34:45.698996408 +0900
+++ /tmp/colcon-0.15.log 2023-11-12 00:34:26.442447239 +0900
@@ -2,11 +2,10 @@
 install/.colcon_install_layout
 install/COLCON_IGNORE
 install/_local_setup_util_sh.py
+install/bin
+install/bin/joint_state_publisher
+install/bin/joint_state_publisher_gui
 install/lib
-install/lib/joint_state_publisher
-install/lib/joint_state_publisher/joint_state_publisher
-install/lib/joint_state_publisher_gui
-install/lib/joint_state_publisher_gui/joint_state_publisher_gui
 install/lib/python3.11
 install/lib/python3.11/site-packages
 install/lib/python3.11/site-packages/joint-state-publisher-gui.egg-link
@@ -31,8 +30,12 @@
 install/share/joint_state_publisher/hook
 install/share/joint_state_publisher/hook/ament_prefix_path.dsv
 install/share/joint_state_publisher/hook/ament_prefix_path.sh
+install/share/joint_state_publisher/hook/path.dsv
+install/share/joint_state_publisher/hook/path.sh
 install/share/joint_state_publisher/hook/pythonpath.dsv
 install/share/joint_state_publisher/hook/pythonpath.sh
+install/share/joint_state_publisher/hook/pythonscriptspath.dsv
+install/share/joint_state_publisher/hook/pythonscriptspath.sh
 install/share/joint_state_publisher/package.bash
 install/share/joint_state_publisher/package.dsv
 install/share/joint_state_publisher/package.sh
@@ -42,8 +45,12 @@
 install/share/joint_state_publisher_gui/hook
 install/share/joint_state_publisher_gui/hook/ament_prefix_path.dsv
 install/share/joint_state_publisher_gui/hook/ament_prefix_path.sh
+install/share/joint_state_publisher_gui/hook/path.dsv
+install/share/joint_state_publisher_gui/hook/path.sh
 install/share/joint_state_publisher_gui/hook/pythonpath.dsv
 install/share/joint_state_publisher_gui/hook/pythonpath.sh
+install/share/joint_state_publisher_gui/hook/pythonscriptspath.dsv
+install/share/joint_state_publisher_gui/hook/pythonscriptspath.sh
 install/share/joint_state_publisher_gui/package.bash
 install/share/joint_state_publisher_gui/package.dsv
 install/share/joint_state_publisher_gui/package.sh


Note that missing files.

Thanks,
-- 
yashi

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'stable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'),
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages colcon depends on:
ii  python3  3.11.4-5+b1
ii  python3-colcon-core  0.15.0-2

Versions of packages colcon recommends:
ii  python3-colcon-argcomplete  0.3.3+ds-2
ii  python3-colcon-bash 0.5.0-1
ii  python3-colcon-cd   0.1.1-2
ii  python3-colcon-cmake0.2.28-1
ii  python3-colcon-defaults 0.2.8-1
ii  python3-colcon-devtools 0.2.5-1
ii  python3-colcon-library-path 0.2.1-2
ii  python3-colcon-metadata 0.2.5-2
ii  python3-colcon-notification 0.2.15+ds-2
ii  python3-colcon-output   0.2.13-1
ii  python3-colcon-package-information  0.3.3-2
ii  python3-colcon-package-selection0.2.10-2
ii  python3-colcon-parallel-executor0.3.0-1
ii  python3-colcon-python-setup-py  0.2.8-1
ii  python3-colcon-recursive-crawl  0.2.3-1
ii  python3-colcon-ros  0.4.1-1
ii  python3-colcon-test-result  0.3.8-2
ii  python3-colcon-zsh  0.5.0-1

colcon suggests no packages.

-- no debconf information



Bug#1055537: colcon: Does not install under bin/

2023-11-09 Thread Yasushi SHOJI
Hi,

I just built a new .deb from source without
debian/patches/0001-Respect-DEB_PYTHON_INSTALL_LAYOUT.patch

It seems it works as I expected.

Best,
-- 
   yashi



Bug#1055537: colcon: Does not install under bin/

2023-11-07 Thread Yasushi SHOJI
Package: colcon
Version: 0.15.0-1
Severity: normal
X-Debbugs-Cc: none, Yasushi SHOJI 

Dear Maintainer,

Colcon 0.15.0-1 doesn't install binaries specified by console_scripts of
entry_points in setup.py.  I've only tested with
generate_parameter_library_py[1] but this problem occurs only with the debian
package.  That is, colcon 0.15.0 from git[2] does work fine for me.

I'm attaching both build logs by .deb and the one I've built but this is
the diff:

```
❯ diff -u log/build_2023-11-08_08-08-40/generate_parameter_library_py/stdout.log
log/build_2023-11-08_08-08-47/generate_parameter_library_py/stdout.log
--- log/build_2023-11-08_08-08-40/generate_parameter_library_py/stdout.log
2023-11-08 08:08:41.721502097 +0900
+++ log/build_2023-11-08_08-08-47/generate_parameter_library_py/stdout.log
2023-11-08 08:08:48.293516763 +0900
@@ -11,9 +11,9 @@
 writing manifest file 'generate_parameter_library_py.egg-info/SOURCES.txt'
 running build_ext
 Creating 
/home/yashi/work/yoshida/avatar-ws/install/lib/python3.11/site-packages/generate-parameter-library-py.egg-link
(link to .)
-Installing generate_parameter_library_cpp script to
/home/yashi/work/yoshida/avatar-ws/install/lib/python3.11/site-packages
-Installing generate_parameter_library_markdown script to
/home/yashi/work/yoshida/avatar-ws/install/lib/python3.11/site-packages
-Installing generate_parameter_library_python script to
/home/yashi/work/yoshida/avatar-ws/install/lib/python3.11/site-packages
+Installing generate_parameter_library_cpp script to
/home/yashi/work/yoshida/avatar-ws/install/bin
+Installing generate_parameter_library_markdown script to
/home/yashi/work/yoshida/avatar-ws/install/bin
+Installing generate_parameter_library_python script to
/home/yashi/work/yoshida/avatar-ws/install/bin

 Installed 
/home/yashi/work/yoshida/avatar-ws/build/generate_parameter_library_py
 running install_data
```

The former is the deb, letter is the colcon I've built from the git
repo.

Hope this helps.

[1]: https://github.com/PickNikRobotics/generate_parameter_library
[2]: https://github.com/colcon/colcon-core/releases/tag/0.15.0

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'stable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'),
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages colcon depends on:
ii  python3  3.11.4-5+b1
ii  python3-colcon-core  0.15.0-1

Versions of packages colcon recommends:
ii  python3-colcon-argcomplete  0.3.3+ds-2
ii  python3-colcon-bash 0.5.0-1
ii  python3-colcon-cd   0.1.1-2
ii  python3-colcon-cmake0.2.28-1
ii  python3-colcon-defaults 0.2.8-1
ii  python3-colcon-devtools 0.2.5-1
ii  python3-colcon-library-path 0.2.1-2
ii  python3-colcon-metadata 0.2.5-2
ii  python3-colcon-notification 0.2.15+ds-2
ii  python3-colcon-output   0.2.13-1
ii  python3-colcon-package-information  0.3.3-2
ii  python3-colcon-package-selection0.2.10-2
ii  python3-colcon-parallel-executor0.3.0-1
ii  python3-colcon-python-setup-py  0.2.8-1
ii  python3-colcon-recursive-crawl  0.2.3-1
ii  python3-colcon-ros  0.4.1-1
ii  python3-colcon-test-result  0.3.8-2
ii  python3-colcon-zsh  0.5.0-1

colcon suggests no packages.

-- no debconf information
-- 
 yashi
running develop
running egg_info
creating generate_parameter_library_py.egg-info
writing generate_parameter_library_py.egg-info/PKG-INFO
writing dependency_links to generate_parameter_library_py.egg-info/dependency_links.txt
writing entry points to generate_parameter_library_py.egg-info/entry_points.txt
writing requirements to generate_parameter_library_py.egg-info/requires.txt
writing top-level names to generate_parameter_library_py.egg-info/top_level.txt
writing manifest file 'generate_parameter_library_py.egg-info/SOURCES.txt'
reading manifest file 'generate_parameter_library_py.egg-info/SOURCES.txt'
writing manifest file 'generate_parameter_library_py.egg-info/SOURCES.txt'
running build_ext
Creating /home/yashi/work/yoshida/avatar-ws/install/lib/python3.11/site-packages/generate-parameter-library-py.egg-link (link to .)
Installing generate_parameter_library_cpp script to /home/yashi/work/yoshida/avatar-ws/install/bin
Installing generate_parameter_library_markdown script to /home/yashi/work/yoshida/avatar-ws/install/bin
Installing generate_parameter_library_python script to /home/yashi/work/yoshida/avatar-ws/install/bin

Installed /home/yashi/work/yoshida/avatar-ws/build/generate_parameter_library_py
running

Bug#1033392: ttylog: ttylog is under /usr/sbin

2023-03-24 Thread Yasushi SHOJI
Package: ttylog
Version: 0.31-1
Severity: normal
X-Debbugs-Cc: none, Yasushi SHOJI 

Dear Maintainer,

ttylog is installed under /usr/sbin.  With a system with a tty which
is group readable, some users don't get ttylog in $PATH.  Please
install it under /usr/bin.

Thanks,

-- System Information:
Debian Release: 12.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages ttylog depends on:
ii  libc6  2.36-8

ttylog recommends no packages.

ttylog suggests no packages.

-- no debconf information



Bug#990850: linux-image-5.10.0-8-amd64: mcba_usb doesn't work

2021-07-25 Thread Yasushi SHOJI
tags 990850 patch
forwarded 990850 https://www.spinics.net/lists/linux-can/msg08120.html

We found the root cause and the fix is on the way to the main line.
https://www.spinics.net/lists/linux-can/msg08125.html
--
yashi



Bug#990850: linux-image-5.10.0-8-amd64: mcba_usb doesn't work

2021-07-09 Thread Yasushi SHOJI
Package: src:linux
Version: 5.10.46-1
Severity: normal
X-Debbugs-Cc: none, Yasushi SHOJI 

Dear Maintainer,

With linux-image-5.10.0-8-amd64, Microchip CAN BUS Analyzer does not
work with mcba_usb device driver.

The same device works with linux-image-5.10.0-7-amd64:

> Jul 09 17:46:58 leno kernel: usb 1-6: USB disconnect, device number 8
> Jul 09 17:46:58 leno kernel: mcba_usb 1-6:1.0 can0: device disconnected
> Jul 09 17:46:58 leno kernel: device can0 left promiscuous mode
> Jul 09 17:47:00 leno kernel: usb 1-6: new full-speed USB device number 12 
> using xhci_hcd
> Jul 09 17:47:00 leno kernel: usb 1-6: New USB device found, idVendor=04d8, 
> idProduct=0a30, bcdDevice= 2.00
> Jul 09 17:47:00 leno kernel: usb 1-6: New USB device strings: Mfr=1, 
> Product=2, SerialNumber=3
> Jul 09 17:47:00 leno kernel: usb 1-6: Product: Microchip CAN BUS Analyzer
> Jul 09 17:47:00 leno kernel: usb 1-6: Manufacturer: Microchip Technology Inc.
> Jul 09 17:47:00 leno kernel: mcba_usb 1-6:1.0 can0: PIC CAN version 2.3
> Jul 09 17:47:00 leno kernel: mcba_usb 1-6:1.0 can0: PIC USB version 2.0
> Jul 09 17:47:00 leno kernel: mcba_usb 1-6:1.0: Microchip CAN BUS Analyzer 
> connected
> Jul 09 17:47:08 leno kernel: IPv6: ADDRCONF(NETDEV_CHANGE): can0: link 
> becomes ready

Please let me know if you need more info.

Best,
--
 yashi

-- Package-specific info:
attached

-- System Information:
Debian Release: 11.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500,
'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages linux-image-5.10.0-8-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.140
ii  kmod28-1
ii  linux-base  4.6

Versions of packages linux-image-5.10.0-8-amd64 recommends:
ii  apparmor 2.13.6-10
ii  firmware-linux-free  20200122-1

Versions of packages linux-image-5.10.0-8-amd64 suggests:
pn  debian-kernel-handbook  
ii  extlinux3:6.04~git20190206.bf6db5b4+dfsg1-3+b1
ii  grub-efi-amd64  2.04-19
pn  linux-doc-5.10  

Versions of packages linux-image-5.10.0-8-amd64 is related to:
ii  firmware-amd-graphics 20210315-2
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
ii  firmware-iwlwifi  20210315-2
pn  firmware-libertas 
ii  firmware-linux-nonfree20210315-2
ii  firmware-misc-nonfree 20210315-2
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
ii  firmware-realtek  20210315-2
pn  firmware-samsung  
pn  firmware-siano
pn  firmware-ti-connectivity  
pn  xen-hypervisor

-- no debconf information
** Version:
Linux version 5.10.0-8-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 
10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP 
Debian 5.10.46-1 (2021-06-24)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64 
root=UUID=c9054a70-0b95-44c7-806d-6dd5d6225151 ro quiet

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

** Kernel log:
[7.968768] usbcore: registered new interface driver usbserial_generic
[7.968776] usbserial: USB Serial support registered for generic
[7.973599] usbcore: registered new interface driver ftdi_sio
[7.973616] usbserial: USB Serial support registered for FTDI USB Serial 
Device
[7.973680] ftdi_sio 1-1.3.2.2:1.0: FTDI USB Serial Device converter detected
[7.973705] usb 1-1.3.2.2: Detected FT2232C
[7.975991] usb 1-1.3.2.2: FTDI USB Serial Device converter now attached to 
ttyUSB0
[7.976253] ftdi_sio 1-1.3.2.2:1.1: FTDI USB Serial Device converter detected
[7.976318] usb 1-1.3.2.2: Detected FT2232C
[7.976618] usb 1-1.3.2.2: FTDI USB Serial Device converter now attached to 
ttyUSB1
[8.263341] audit: type=1400 audit(1625821110.310:34): apparmor="DENIED" 
operation="capable" profile="libvirtd" pid=810 comm="daemon-init" capability=17 
 capname="sys_rawio"
[8.542100] rfkill: input handler disabled
[9.512441] e1000e :00:1f.6 enp0s31f6: NIC Link is Up 1000 Mbps Full 
Duplex, Flow Control: Rx/Tx
[9.512527] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s31f6: link becomes ready
[   10.687617] wlp3s0: authentica

Bug#841028: Same behaviour but triggered when two network present

2019-03-19 Thread Yasushi SHOJI
My system now behaves as described above.
A only difference is that I have wired and wireless network.
When I enable both interfaces, cups takes 100 % CPU.

I think I can take some debug info if needed.

Thanks,

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

Kernel: Linux 4.19.0-4-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 cups-browsed depends on:
ii  cups-daemon   2.2.10-4
ii  libavahi-client3  0.7-4+b1
ii  libavahi-common3  0.7-4+b1
ii  libavahi-glib10.7-4+b1
ii  libc6 2.28-8
ii  libcups2  2.2.10-4
ii  libcupsfilters1   1.21.6-4
ii  libglib2.0-0  2.58.3-1
ii  libldap-2.4-2 2.4.47+dfsg-3
ii  lsb-base  10.2019031300

Versions of packages cups-browsed recommends:
ii  avahi-daemon  0.7-4+b1

cups-browsed suggests no packages.

-- no debconf information
-- 
 yashi



Bug#922017: pipenv: Unable to use with Python 3.6

2019-02-11 Thread Yasushi SHOJI
https://github.com/pypa/pip/issues/5367

There is similar issue on github.  I think that we have to provide
python3-distutils for 3.6?  I've just downgraded it with
python3-distutils_3.6.6-1_all.deb and pipenv worked.

$ sudo dpkg -i /tmp/downloads/python3-distutils_3.6.6-1_all.deb
dpkg: warning: downgrading python3-distutils from 3.7.2-3 to 3.6.6-1
(Reading database ... 351861 files and directories currently installed.)
Preparing to unpack .../python3-distutils_3.6.6-1_all.deb ...
Unpacking python3-distutils (3.6.6-1) over (3.7.2-3) ...
Setting up python3-distutils (3.6.6-1) ...

pipenv --python 3.6
Creating a virtualenv for this project…
Using /usr/bin/python3.6m (3.6.8) to create virtualenv…
⠋Running virtualenv with interpreter /usr/bin/python3.6m
Using base prefix '/usr'
New python executable in /tmp/pipenv-test/.venv/bin/python3.6m
Also creating executable in /tmp/pipenv-test/.venv/bin/python
Installing setuptools, pkg_resources, pip, wheel...done.

Virtualenv location: /tmp/pipenv-test/.venv
$

So, I guess when Debian dropped 3.6 support, python3-distutils also removed 3.6?
-- 
yashi



Bug#922017: pipenv: Unable to use with Python 3.6

2019-02-11 Thread Yasushi SHOJI
Package: pipenv
Version: 11.9.0-1
Severity: normal

Dear Maintainer,

I've been using pipenv with Python 3.4, which I installed from
snapshot.debian.net on my Debian Sid.

Today I tried to run it with Python 3.6, which is still available in the
debian archive[1].  But got the following error.

All you have to do is run

$ pipenv --python 3.6

Does Debian supports multiple version of Python, anyway?  If so, is
there a chance that this bug(?) will be fixed?

[1]: 
https://packages.debian.org/search?keywords=python3.5=names=1=all=all

Thanks,
--
 yashi



-- Installed package for Python 3.6
ii  libpython3.6:amd64   3.6.8-1
ii  libpython3.6-dev:amd64   3.6.8-1
ii  libpython3.6-minimal:amd64   3.6.8-1
ii  libpython3.6-stdlib:amd643.6.8-1
ii  python3.63.6.8-1
ii  python3.6-dev3.6.8-1
ii  python3.6-minimal3.6.8-1




-- Log
$ pipenv --python 3.6
Creating a virtualenv for this project…
Using /usr/bin/python3.6m (3.6.8) to create virtualenv…
⠋Running virtualenv with interpreter /usr/bin/python3.6m
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/virtualenv.py", line 25, in 
import distutils.sysconfig
ModuleNotFoundError: No module named 'distutils.sysconfig'

Virtualenv location: /tmp/pipenv-test/.venv
Creating a Pipfile for this project…
Traceback (most recent call last):
  File "/usr/bin/pipenv", line 11, in 
load_entry_point('pipenv==11.9.0', 'console_scripts', 'pipenv')()
  File "/usr/lib/python3/dist-packages/pipenv/vendor/click/core.py",
line 722, in __call__
return self.main(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/pipenv/vendor/click/core.py",
line 697, in main
rv = self.invoke(ctx)
  File "/usr/lib/python3/dist-packages/pipenv/vendor/click/core.py",
line 1043, in invoke
return Command.invoke(self, ctx)
  File "/usr/lib/python3/dist-packages/pipenv/vendor/click/core.py",
line 895, in invoke
return ctx.invoke(self.callback, **ctx.params)
  File "/usr/lib/python3/dist-packages/pipenv/vendor/click/core.py",
line 535, in invoke
return callback(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/pipenv/vendor/click/decorators.py",
line 17, in new_func
return f(get_current_context(), *args, **kwargs)
  File "/usr/lib/python3/dist-packages/pipenv/cli.py", line 235, in cli
three=three, python=python, warn=True, site_packages=site_packages
  File "/usr/lib/python3/dist-packages/pipenv/core.py", line 636, in
ensure_project
ensure_pipfile(validate=validate, skip_requirements=skip_requirements)
  File "/usr/lib/python3/dist-packages/pipenv/core.py", line 289, in
ensure_pipfile
project.create_pipfile(python=python)
  File "/usr/lib/python3/dist-packages/pipenv/project.py", line 518,
in create_pipfile
'python_version': python_version(required_python)[: len('2.7')]
TypeError: 'NoneType' object is not subscriptable




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

Kernel: Linux 4.19.0-2-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 pipenv depends on:
ii  python3   3.7.2-1
ii  python3-certifi   2018.8.24-1
ii  python3-pip   18.1-4
ii  python3-pkg-resources 40.7.1-1
ii  python3-virtualenv15.1.0+ds-2
ii  python3-virtualenv-clone  0.3.0-1.2

pipenv recommends no packages.

pipenv suggests no packages.

-- no debconf information



Bug#907461: gcc-arm-none-eabi: Provide Big-Endian libgcc

2018-08-28 Thread Yasushi SHOJI
Package: gcc-arm-none-eabi
Version: 15:7-2018-q2-3
Severity: wishlist

Dear Maintainer,

It'd be nice if gcc-arm-none-eabi could be used for Big-Endian MCUs.

arm-none-eabi-gcc already has support for `-mbig-endian` and `-Wl,-EB`
but `gcc-arm-none-eabi` package doesn't have `libgcc.a` compiled for
big-endian.

Well, not quite right.  There seems to be one big-endian libgcc.a:
`/usr/lib/gcc/arm-none-eabi/7.3.1/thumb/v7-ar/fpv3/hard/be/libgcc.a`.
But not others.

Would you mind to provide us big-endian variant of libgcc.a for other
configuration?

Thanks,
--
   yashi


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

Kernel: Linux 4.17.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 gcc-arm-none-eabi depends on:
ii  binutils-arm-none-eabi  2.31.1-2+10
ii  libc6   2.27-5
ii  libgcc1 1:8.2.0-4
ii  libgmp102:6.1.2+dfsg-3
ii  libisl150.18-4
ii  libmpc3 1.1.0-1
ii  libmpfr64.0.1-1
ii  libstdc++6  8.2.0-4
ii  zlib1g  1:1.2.11.dfsg-1

Versions of packages gcc-arm-none-eabi recommends:
ii  libnewlib-arm-none-eabi  3.0.0.20180802-2

gcc-arm-none-eabi suggests no packages.

-- no debconf information



Bug#837146: [gnome-tweak-tool] press alt key make gnome-tweak-tool crash

2018-02-12 Thread Yasushi SHOJI
Hi guys,

I can reproduce this problem on my Sid, so I fire up gdb to see what's
going on.  It seems to me that ibus is causing Gdk Window to be NULL.
When I removed ibus, ibus-skk and im-config from my system, GNOME
Tweaks doesn't crash anymore.

Đặng, didn't you have some input method loaded?

Detail (gdb debug seesion log) is attached.

Thanks,
--
  yashi
Source directories searched: /tmp/gtk+3.0-3.22.26/gdk:$cdir:$cwd
Reading symbols from /usr/bin/python3...Reading symbols from 
/usr/lib/debug/.build-id/e7/1f68741e22cb60c0c643ecb4feff0a38af8a5e.debug...done.
done.
Starting program: /usr/bin/python3 /usr/bin/gnome-tweaks
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffec37e700 (LWP 17520)]
[New Thread 0x7fffebb7d700 (LWP 17521)]
[New Thread 0x7fffeb16f700 (LWP 17522)]
[New Thread 0x7fffe8b62700 (LWP 17524)]
[New Thread 0x7fffdbfff700 (LWP 17525)]
[New Thread 0x7fffcd22b700 (LWP 17527)]
[New Thread 0x7fffcca2a700 (LWP 17528)]
[New Thread 0x7fffc7fff700 (LWP 17530)]
[Thread 0x7fffe8b62700 (LWP 17524) exited]
[Thread 0x7fffdbfff700 (LWP 17525) exited]

Thread 1 "python3" received signal SIGSEGV, Segmentation fault.
0x73c2a102 in gdk_window_has_impl (window=) at 
../../../../gdk/gdkwindow.c:677
677 {
672 window->parent->window_type == GDK_WINDOW_ROOT;
673 }
674 
675 gboolean
676 _gdk_window_has_impl (GdkWindow *window)
677 {
678   return gdk_window_has_impl (window);
679 }
680 
681 static gboolean
$1 = 
#0  0x73c2a102 in gdk_window_has_impl (window=) at 
../../../../gdk/gdkwindow.c:677
#1  0x73c2a102 in _gdk_window_has_impl (window=window@entry=0x0) at 
../../../../gdk/gdkwindow.c:678
#2  0x73c615ee in gdk_x11_window_get_xid (window=0x0) at 
../../../../../gdk/x11/gdkwindow-x11.c:5560
#3  0x7fffe8dc41ab in gtk_im_context_xim_filter_keypress (context=0xca61e0 
[GtkIMContextXIM], event=0x1e87000)
at ../../../../../modules/input/gtkimcontextxim.c:673
#4  0x7fffeed56af3 in gtk_im_multicontext_filter_keypress (context=0xf570c0 
[GtkIMMulticontext], event=0x1e87000)
at ../../../../gtk/gtkimmulticontext.c:359
#5  0x75c7afce in ffi_call_unix64 () at ../src/x86/unix64.S:76
#6  0x75c7a93f in ffi_call (cif=cif@entry=0x1dd4268, fn=, rvalue=, 
rvalue@entry=0x7fffce08, avalue=) at 
../src/x86/ffi64.c:525
#7  0x7667adda in pygi_invoke_c_callable (function_cache=0x1dd41c0, 
state=, py_args=, py_kwargs=) at 
../../gi/pygi-invoke.c:682
#8  0x7667c9b8 in pygi_function_cache_invoke (function_cache=, py_args=py_args@entry=(, ), py_kwargs=) at 
../../gi/pygi-cache.c:863
#9  0x7667b648 in pygi_callable_info_invoke (info=, 
py_args=py_args@entry=(, ), kwargs=, cache=, 
user_data=user_data@entry=0x0) at ../../gi/pygi-invoke.c:725
#10 0x7667b67f in _wrap_g_callable_info_invoke (self=, 
py_args=py_args@entry=(, ), kwargs=) at ../../gi/pygi-invoke.c:762
#11 0x76670c29 in _callable_info_call (self=0x7fffec5945a8, 
args=(,), kwargs=0x0)
at ../../gi/pygi-info.c:561
#12 0x0045a0d3 in _PyObject_FastCallDict (func=, args=0x7fffdb7c5928, nargs=1, kwargs=0x0)
at ../Objects/abstract.c:2331
#13 0x0054fc17 in call_function 
(pp_stack=pp_stack@entry=0x7fffd038, oparg=, 
kwnames=kwnames@entry=0x0)
at ../Python/ceval.c:4848
#14 0x005545af in _PyEval_EvalFrameDefault (f=, 
throwflag=) at ../Python/ceval.c:3322
#15 0x0054efe8 in PyEval_EvalFrameEx (throwflag=0, f=Frame 
0x7fffdb7c5788, for file /usr/lib/python3/dist-packages/gtweak/tweakview.py, 
line 196, in _after_key_press (self=, '__spec__': , 
origin='/usr/lib/python3/dist-packages/gtweak/tweakview.py', loader_state=None, 
submodule_search_locations=None, _set_fileattr=True, 
_cached='/usr/lib/python3/dist-packages/gtweak/__pycache__/tweakview.cpython-36.pyc',
 _initializing=False) at 

Bug#888808: gnome-calculator: black rectangle

2018-01-29 Thread Yasushi SHOJI
Package: gnome-calculator
Version: 3.26.0-3+b1
Severity: normal

Dear Maintainer,

GNOME Calculator 3.26.0-3+b1 gets a black rectangle at very left in the
input box after the last update.

Adding a small screenshot.


-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf

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 gnome-calculator depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.1-3
ii  libatk1.0-0  2.26.1-3
ii  libc62.26-6
ii  libcairo-gobject21.15.8-3
ii  libcairo21.15.8-3
ii  libgdk-pixbuf2.0-0   2.36.11-1
ii  libglib2.0-0 2.54.3-2
ii  libgmp10 2:6.1.2+dfsg-2
ii  libgtk-3-0   3.22.26-2
ii  libgtksourceview-3.0-1   3.24.6-1
ii  libmpc3  1.1.0-1
ii  libmpfr6 4.0.0-5
ii  libpango-1.0-0   1.40.14-1
ii  libpangocairo-1.0-0  1.40.14-1
ii  libsoup2.4-1 2.60.3-1
ii  libxml2  2.9.4+dfsg1-6.1

Versions of packages gnome-calculator recommends:
ii  gvfs  1.34.1-2
ii  yelp  3.26.0-2

gnome-calculator suggests no packages.

-- no debconf information


Bug#888249: gnome-calculator: die on startup with "MPFR assertion failed"

2018-01-24 Thread Yasushi SHOJI
Package: gnome-calculator
Version: 3.26.0-3
Severity: normal

Dear Maintainer,

   * What led up to the situation?
 - just run gnome-calculator on a console.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 - run gnome-calculator on gnome-terminal

   * What was the outcome of this action?
 - abort with the following output:
   ../../src/init2.c:52: MPFR assertion failed: p >= 2 && p <= 
((mpfr_prec_t)((mpfr_uprec_t)(~(mpfr_uprec_t)0)>>1))
   zsh: abort  gnome-calculator
  
   * What outcome did you expect instead?
 - running fine

Here is a back trace just in case.

$ gdb =gnome-calculator
GNU gdb (Debian 7.12-6+b1) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/gnome-calculator...Reading symbols from 
/usr/lib/debug/.build-id/5f/9717d3e0d439032714dfa9a390b38d52039abe.debug...done.
done.
(gdb) r
Starting program: /usr/bin/gnome-calculator 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe95af700 (LWP 31360)]
[New Thread 0x7fffe8dae700 (LWP 31361)]
[New Thread 0x7fffe2971700 (LWP 31362)]
../../src/init2.c:52: MPFR assertion failed: p >= 2 && p <= 
((mpfr_prec_t)((mpfr_uprec_t)(~(mpfr_uprec_t)0)>>1))

Thread 1 "gnome-calculato" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  0x75c0e6a0 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:51
#1  0x75c0fcf7 in __GI_abort () at abort.c:90
#2  0x70838ea9 in mpfr_assert_fail () at 
/usr/lib/x86_64-linux-gnu/libmpfr.so.4
#3  0x7082ece0 in mpfr_init2 () at 
/usr/lib/x86_64-linux-gnu/libmpfr.so.4
#4  0x705ea673 in mpc_init3 (x=, prec_re=, prec_im=) at init3.c:27
#5  0x705efb52 in mpc_pow_usi_naive (z=z@entry=0x55ba9f60, 
x=x@entry=0x55babd20, y=y@entry=3, sign=sign@entry=-1, rnd=rnd@entry=0) at 
pow_ui.c:31
#6  0x705efc6c in mpc_pow_usi (z=0x55ba9f60, x=0x55babd20, y=3, 
sign=-1, rnd=0) at pow_ui.c:77
#7  0x761e18b8 in number_xpowy_integer (self=self@entry=0x55babd60 
[Number], n=-3) at number.c:1239
#8  0x761e5156 in serializer_cast_to_string_real (self=0x559e4a10 
[Serializer], x=0x55ba9f40 [Number], number_base=10, force_sign=0, 
n_digits=0x7fffcc54, string=0x55977ee0) at serializer.c:859
#9  0x761e56db in serializer_cast_to_string 
(self=self@entry=0x559e4a10 [Serializer], x=x@entry=0x55ba0100 
[Number], n_digits=n_digits@entry=0x7fffcc54) at serializer.c:652
#10 0x761e5ff1 in serializer_to_string (self=0x559e4a10 
[Serializer], x=x@entry=0x55ba0100 [Number])
at serializer.c:291
#11 0x761e7870 in unit_format (self=self@entry=0x55870840 [Unit], 
x=x@entry=0x55ba0100 [Number]) at unit.c:2370
#12 0x55566dd2 in math_converter_update_result_label 
(self=self@entry=0x55aec180 [MathConverter])
at math-converter.c:367
#13 0x55566ed1 in math_converter_to_combobox_changed_cb 
(self=0x55aec180 [MathConverter]) at math-converter.c:811
#14 0x55566ed1 in 
_math_converter_to_combobox_changed_cb_gtk_combo_box_changed 
(_sender=, self=0x55aec180) at math-converter.c:817
#18 0x76742ebf in  (instance=, signal_id=, 
detail=) at ../../../../gobject/gsignal.c:3447
#15 0x76726f9d in g_closure_invoke (closure=0x55ab3350, 
return_value=0x0, n_param_values=1, param_values=0x7fffcef0, 
invocation_hint=0x7fffce70) at ../../../../gobject/gclosure.c:804
#16 0x76739cce in signal_emit_unlocked_R 
(node=node@entry=0x55ad0a50, detail=detail@entry=0, 
instance=instance@entry=0x55aee510, 
emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fffcef0)
at ../../../../gobject/gsignal.c:3635
#17 0x767424a5 in g_signal_emit_valist (instance=0x55aee510, 
signal_id=, detail=0, var_args=var_args@entry=0x7fffd0b0) at 
../../../../gobject/gsignal.c:3391
#19 0x773804a5 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#20 0x77382a85 in gtk_combo_box_set_active () at 

Bug#870254: icecc: please support systemd

2017-07-31 Thread Yasushi SHOJI
Package: icecc
Version: 1.0.1-2+b2
Severity: normal

Dear Maintainer,

icecc doesn't seem to work under systemd.

Here is a link to fedora's:

https://lists.fedoraproject.org/pipermail/scm-commits/2012-February/731640.html

Hoping we'll have icecc working again on Debian.

Thanks,
-- 
   yashi

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf, armel

Kernel: Linux 4.11.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 icecc depends on:
ii  adduser 3.115
ii  clang-3.7 [c-compiler]  1:3.7.1-3+b2
ii  clang-3.8 [c-compiler]  1:3.8.1-24
ii  clang-3.9 [c-compiler]  1:3.9.1-10
ii  clang-4.0 [c-compiler]  1:4.0.1-1
ii  clang-5.0 [c-compiler]  1:5.0~svn305653-1
ii  file1:5.30-1
ii  g++ [c++-compiler]  4:6.3.0-4d1
ii  g++-5 [c++-compiler]5.4.1-11
ii  g++-6 [c++-compiler]6.4.0-2
ii  g++-7 [c++-compiler]7.1.0-10
ii  gcc [c-compiler]4:6.3.0-4d1
ii  gcc-4.4 [c-compiler]4.4.7-8
ii  gcc-4.6 [c-compiler]4.6.4-7
ii  gcc-4.7 [c-compiler]4.7.4-3
ii  gcc-4.8 [c-compiler]4.8.5-4
ii  gcc-4.9 [c-compiler]4.9.4-2
ii  gcc-5 [c-compiler]  5.4.1-11
ii  gcc-6 [c-compiler]  6.4.0-2
ii  gcc-7 [c-compiler]  7.1.0-10
ii  libc6   2.24-12
ii  libgcc1 1:7.1.0-10
ii  libstdc++6  7.1.0-10
ii  lsb-base9.20161125
ii  tcc [c-compiler]0.9.27~git20161217.cd9514ab-3

Versions of packages icecc recommends:
ii  logrotate  3.11.0-0.1

Versions of packages icecc suggests:
ii  icecc-monitor  3.1.0-1

-- no debconf information



Bug#863663: libgstreamer1.0-0: plays MJPEG AVI files (and possibly other formats) at degraded quality

2017-06-26 Thread Yasushi SHOJI
Hi,

On Sun, Jun 25, 2017 at 2:50 AM, Francesco Poli 
wrote:
>
> On Wed, 21 Jun 2017 21:52:43 +0200 Francesco Poli wrote:
>
> [...]
> > At this point I really cannot understand what's going on and why all my
> > attempts are failing...   :-(
>
> Could someone please shed some light on this mystery?

I might be misunderstanding but the following pipeline seems to work
here without any
ranking change on my Debian Sid.

$ gst-launch-1.0 -v filesrc location=wave_anim.avi ! avidemux ! jpegparse !
avdec_mjpeg ! videoconvert ! autovideosink

and Yes, I can reproduce the degraded image with jpegdec

$ gst-launch-1.0 -v filesrc location=wave_anim.avi ! avidemux ! jpegparse !
jpegdec ! autovideosink

I'm using 1.12.1 it that matters.

$ gst-launch-1.0 --version
gst-launch-1.0 version 1.12.1
GStreamer 1.12.1
-- 
  yashi


Bug#848669: devhelp: Unusably slow

2017-03-28 Thread Yasushi SHOJI
Hi,

I seem to me that the slowness I've seen isn't devhelp, but webkit2 /
webkit2gtk.

WEBKIT_DISABLE_COMPOSITING_MODE=1 helped a lot.

ref. https://lists.webkit.org/pipermail/webkit-gtk/2016-September/002803.html
-- 
yashi



Bug#858823: check: new version 0.11 is available

2017-03-27 Thread Yasushi SHOJI
Package: check
Version: 0.10.0-3+b3
Severity: wishlist

Dear Maintainer,

A new version, 0.11.0, is released on Dec 18, 2016.  Please update if
you have time.

https://github.com/libcheck/check/releases/tag/0.11.0

Thanks,

-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf, armel

Kernel: Linux 4.9.0-2-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 check depends on:
ii  dpkg1.18.23
ii  install-info6.3.0.dfsg.1-1+b2
ii  libsubunit-dev  1.1.0-3
ii  mawk1.3.3-17+b3

check recommends no packages.

check suggests no packages.

-- no debconf information
-- 
 yashi



Bug#848669: devhelp: Unusably slow

2016-12-19 Thread Yasushi SHOJI
Package: devhelp
Version: 3.22.0-1
Severity: normal

Dear Maintainer,

I've just noticed that devhelp is unusably slow to react to user intput.

Just run devhelp (either from GNOME Shell or command line prompt) and
click or scroll, you should see the slowness.  I'ts slow but top or
htop don't show CPU usage.  Rather, it feels like it's not getting
events from X.

I've tried to run Jessie version of devhelp but it seg faults.  Also
tried experimental version of libwebkit2gtk-4.0-37, but didn't change.

I also noticed that epiphany-browser is scrolling slow.  So, it might
not be devhelp's fault but common libraries have some issue.

Thanks,

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf, armel

Kernel: Linux 4.8.0-2-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 devhelp depends on:
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-8
ii  libcairo-gobject21.14.8-1
ii  libcairo21.14.8-1
ii  libdevhelp-3-2   3.22.0-1
ii  libgdk-pixbuf2.0-0   2.36.1-1
ii  libglib2.0-0 2.50.2-2
ii  libgtk-3-0   3.22.5-1
ii  libjavascriptcoregtk-4.0-18  2.14.2-1
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libsoup2.4-1 2.56.0-1
ii  libwebkit2gtk-4.0-37 2.14.2-1

Versions of packages devhelp recommends:
ii  libglib2.0-doc   2.50.2-2
ii  libgtk-3-doc 3.22.5-1
ii  libpango1.0-doc  1.40.3-3

devhelp suggests no packages.

-- no debconf information
-- 
 yashi



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

2016-09-13 Thread Yasushi SHOJI
On Thu, 08 Sep 2016 10:38:09 +0900,
Leon Meier wrote:
> 
> By the way, I don't know who is the culprit: libgtk-3-0, emacs, or
> someone else. So please consider my found / nofound tags just as
> additional information on my configuration rather as a bug source
> hint. Sorry about that.

https://mail.gnome.org/archives/commits-list/2016-May/msg06553.html

I found this commit on Gtk+. So I assume this is an intended change
for Gtk+ 3.22, no?
--
   yashi



Bug#814982: [xwayland] Reproducible segmentation fault when pluggin new screen

2016-03-01 Thread Yasushi SHOJI
On Wed, 02 Mar 2016 08:05:07 +0900,
Julian Andres Klode wrote:
> 
> This could be related / the fix:
> 
> https://cgit.freedesktop.org/xorg/xserver/commit/?id=2116f03be04240e961649ca750a7aa5438b8446c

Indeed.  The commit fixed the problem on my system.
Thanks,
--
   yashi



Bug#814982: [xwayland] Reproducible segmentation fault when pluggin new

2016-02-22 Thread Yasushi SHOJI
Hi,

I'm seeing the same problem for last few weeks.  The backtrace is
basically the same.

No new info from me but just to let you know that it segfaults here
too.
-- 
  yashi



Bug#783792: attaching a patch

2015-04-30 Thread Yasushi SHOJI
Tags: patch

From 954297ac66735f9fa8788f22afd63b84d9df35f7 Mon Sep 17 00:00:00 2001
From: Yasushi SHOJI ya...@atmark-techno.com
Date: Thu, 30 Apr 2015 16:33:17 +0900
Subject: [PATCH] Disable 'Device' section diff in stat output

While using debbindiff with file system images mounted with different
loop devices, stat shows that those loop devices are indeed
different. This clutters the report if you are comparing many files and
unable to see important points.

Usually those devices does not matter when comparing files for
reproducible build, so disable the device diff.
---
 debbindiff/comparators/directory.py | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/debbindiff/comparators/directory.py 
b/debbindiff/comparators/directory.py
index d296b22..aeece5a 100644
--- a/debbindiff/comparators/directory.py
+++ b/debbindiff/comparators/directory.py
@@ -36,10 +36,12 @@ class Stat(Command):
 return ['stat', self.path]
 
 FILE_RE = re.compile(r'^\s*File:.*$')
+DEVICE_RE = re.compile(r'Device: [0-9a-f]+h/[0-9]+d')
 INODE_RE = re.compile(r'Inode: [0-9]+')
 
 def filter(self, line):
 line = Stat.FILE_RE.sub('', line)
+line = Stat.DEVICE_RE.sub('', line)
 line = Stat.INODE_RE.sub('', line)
 return line
 
-- 
2.4.0.rc3.3.g6eb1401



Bug#783792: debbindiff: Ignore 'Device' section in stat output

2015-04-30 Thread Yasushi SHOJI
Package: debbindiff
Version: 16
Severity: wishlist

Dear Maintainer,

I'd like to disable the Device section diff in the stat output.  This
feature is needed when I compare different image files I've been
verifing.

In a conversation in the #debian-reproducible IRC channel on OFTC, I
was told to disable device section by default (with out any option). 

I will post a patch soon.  Meanwhile, here is a github repo for this:
https://github.com/yashi/debbindiff/commits/master


-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, armel

Kernel: Linux 4.0.0-trunk-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 debbindiff depends on:
ii  python 2.7.9-1
ii  python-debian  0.1.27
ii  python-magic   1:5.22+15-2
ii  python-rpm 4.11.3-1.1

Versions of packages debbindiff recommends:
ii  acl 2.2.52-2
ii  binutils-multiarch  2.25-7
ii  bzip2   1.0.6-7+b3
ii  cpio2.11+dfsg-4.1
ii  file1:5.22+15-2
ii  fontforge-extras0.3-4
ii  gettext 0.19.3-2
ii  ghc 7.8.4-1
ii  gnupg   1.4.18-7
ii  pdftk   2.02-2
ii  poppler-utils   0.26.5-2
ii  rpm2cpio4.11.3-1.1
ii  sng 1.0.6-2
ii  squashfs-tools  1:4.2+20130409-2
ii  unzip   6.0-16
ii  vim-common  2:7.4.712-1
ii  xz-utils5.1.1alpha+20120614-2+b3

debbindiff suggests no packages.

-- 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#763486: Acknowledgement (nvidia-texture-tools: Please change build dependency to libjpeg-dev (libjpeg-turbo transition))

2014-10-06 Thread Yasushi SHOJI
hmm I assume I was confused.  Sorry for a false alart.
All seems to be fine.

$ dpkg -l libnvtt2
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersionArchitecture   
Description
+++-===-==-==-
ii  libnvtt2:amd64  2.0.8-1+dfsg-5 amd64  NVIDIA 
Texture Tools

$ debsums libnvtt2
/usr/lib/x86_64-linux-gnu/libnvcore.so.2.0.8  OK
/usr/lib/x86_64-linux-gnu/libnvimage.so.2.0.8 OK
/usr/lib/x86_64-linux-gnu/libnvmath.so.2.0.8  OK
/usr/lib/x86_64-linux-gnu/libnvtt.so.2.0.8OK
/usr/share/doc/libnvtt2/NVIDIA_Texture_Tools_README.txt.gzOK
/usr/share/doc/libnvtt2/changelog.Debian.gz   OK
/usr/share/doc/libnvtt2/changelog.gz  OK
/usr/share/doc/libnvtt2/copyright OK

$ ldd /usr/lib/x86_64-linux-gnu/libnvtt.so.2.0.8 | grep libjpeg
libjpeg.so.62 = /usr/lib/x86_64-linux-gnu/libjpeg.so.62 
(0x7f4f4c87d000)


Now re-install 2.0.8-1+dfsg-4+b2

$ sudo apt-get install libnvtt2=2.0.8-1+dfsg-4+b2 libnvtt-dev=2.0.8-1+dfsg-4+b2
   :
$ dpkg -l libnvtt2
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersionArchitecture   
Description
+++-===-==-==-
ii  libnvtt2:amd64  2.0.8-1+dfsg-4+b2  amd64  NVIDIA 
Texture Tools

$ debsums libnvtt2
/usr/lib/x86_64-linux-gnu/libnvcore.so.2.0.8  OK
/usr/lib/x86_64-linux-gnu/libnvimage.so.2.0.8 OK
/usr/lib/x86_64-linux-gnu/libnvmath.so.2.0.8  OK
/usr/lib/x86_64-linux-gnu/libnvtt.so.2.0.8OK
/usr/share/doc/libnvtt2/NVIDIA_Texture_Tools_README.txt.gzOK
/usr/share/doc/libnvtt2/changelog.Debian.amd64.gz OK
/usr/share/doc/libnvtt2/changelog.Debian.gz   OK
/usr/share/doc/libnvtt2/changelog.gz  OK
/usr/share/doc/libnvtt2/copyright OK

$ ldd /usr/lib/x86_64-linux-gnu/libnvtt.so.2.0.8 | grep libjpeg
libjpeg.so.8 = /usr/lib/x86_64-linux-gnu/libjpeg.so.8 
(0x7fbb71965000)
libjpeg.so.62 = /usr/lib/x86_64-linux-gnu/libjpeg.so.62 
(0x7fbb6f973000)



So, 2.0.8-1+dfsg-5 is linked only against libjpeg.so.62 (libjpeg
turbo), but 2.0.8-1+dfsg-4+b2 had both. I thought the other way
around.



At Mon, 06 Oct 2014 02:14:24 +0200,
Lennart Weller wrote:
 
 Did you rebuild the nvidia-texture-tools on your PC? Because the
 library in the package is only linked against jpeg.so.62. Because of
 the way cmake includes the jpeg libraries
 right now it will probably include both if it finds them.
 I will fix the build process over the next days to avoid this.
 
 Lennart
 
 Am 05.10.2014 19:10, schrieb Yasushi SHOJI:
  On Sat, 04 Oct 2014 16:54:21 +0200 Lennart Weller l...@ring0.de wrote:
  I quickly tested the compression/decompression and use of the library in
  games with the libjpeg-turbo and couldn't find any faults. The new
  version is now available in unstable.
  Just rebuilt 0ad with new libnvtt2:amd64 installed and I see the
  following message when linking:
  
  /usr/bin/ld: warning: libjpeg.so.62, needed by 
  /usr/lib/x86_64-linux-gnu/libnvtt.so, may conflict with libjpeg.so.8
  
  ldd on libnvtt.so.2.0.8 shows me that the version 2.0.8-1+dfsg-5 of it
  is linked against both libjpeg62 and libjpeg.so.8.  Is this norm?
  
  Thanks,
 


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



Bug#763486: Acknowledgement (nvidia-texture-tools: Please change build dependency to libjpeg-dev (libjpeg-turbo transition))

2014-10-05 Thread Yasushi SHOJI
On Sat, 04 Oct 2014 16:54:21 +0200 Lennart Weller l...@ring0.de wrote:
 I quickly tested the compression/decompression and use of the library in
 games with the libjpeg-turbo and couldn't find any faults. The new
 version is now available in unstable.

Just rebuilt 0ad with new libnvtt2:amd64 installed and I see the
following message when linking:

/usr/bin/ld: warning: libjpeg.so.62, needed by 
/usr/lib/x86_64-linux-gnu/libnvtt.so, may conflict with libjpeg.so.8

ldd on libnvtt.so.2.0.8 shows me that the version 2.0.8-1+dfsg-5 of it
is linked against both libjpeg62 and libjpeg.so.8.  Is this norm?

Thanks,
-- 
 yashi


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



Bug#690842: ddskk: affects load-theme background color

2012-10-18 Thread Yasushi SHOJI
Package: ddskk
Version: 14.4-3
Severity: normal

Dear Maintainer,

If I install ddskk, load-theme in emacs24 does not work properly.  That
is, even if you select tango dark theme, the background color stays
white.

This is reproduceable with package installation and removal.

1) install ddskk and emacs24
   sudo apt-get install ddskk emacs24

2) run emacs24 with --no-init-file
   emacs24 --no-init-file

3) load tango-dark theme
   M-x load-theme tango-dark

Let me know if you need more info.

Thanks,

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (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 ddskk depends on:
ii  apel  10.8-2
ii  dpkg  1.16.8
ii  emacs24   24.2+1-1
ii  install-info  4.13a.dfsg.1-10

Versions of packages ddskk recommends:
ii  skkdic  20110529-1

Versions of packages ddskk suggests:
ii  dictionaries-common  1.12.10
pn  eieionone
pn  kakasi   none
pn  lookup-elnone
ii  ruby1.8  1.8.7.358-5
ii  skkdic   20110529-1
pn  skkdic-extra none
pn  skktools none
pn  w3m-el   none

-- 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#592125: ht: wrong display size for some of the Elf64_Shdr's member variables

2010-08-07 Thread Yasushi SHOJI
Package: ht
Version: 2.0.18-1
Severity: normal

Hi,

hte's section header window (F6-elf/section headers) seems to have
wrong size for link, info, alignment, and entsize.

it displays

[-] section 1: .interp   │
│  name string index000b│
│  type 0001 (progbits) │
│  flags0002 details│
│  address  00400200│
│  offset   0200│
│  size 001c│
│  link │
│  info │
│  alignment│
│  entsize  │

instead of

 :
│  link │
│  info │
│  alignment│
│  entsize  │

as you can see elf64 bit spec[1], link and info is 32 bit width
(Elf64_Word), and alignment and entsize is 64 bit width
(Elf64_Xword). And HT editor have them right in its own section header
structure

taken from elfstruc.h:
 struct ELF_SECTION_HEADER64 {
 elf64_half sh_name;
 elf64_half sh_type;
 elf64_word sh_flags;
 elf64_addr sh_addr;
 elf64_off sh_offset;
 elf64_word sh_size;
 elf64_half sh_link;
 elf64_half sh_info;
 elf64_word sh_addralign;
 elf64_word sh_entsize;
 };

so, I thought it might be just display widths, and edit
elfsectionheader64 in htelfshs.cc.  but it seems it gets wrong value.

hope someone have time to look at it.

[1]: http://downloads.openwatcom.org/ftp/devel/docs/elf-64-gen.pdf

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (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/bash

Versions of packages ht depends on:
ii  dpkg  1.15.8.3   Debian package management system
ii  install-info  4.13a.dfsg.1-5 Manage installed documentation in 
ii  libc6 2.11.2-2   Embedded GNU C Library: Shared lib
ii  libgcc1   1:4.4.4-8  GCC support library
ii  liblzo2-2 2.03-2 data compression library
ii  libncurses5   5.7+20100313-2 shared libraries for terminal hand
ii  libstdc++64.4.4-8The GNU Standard C++ Library v3
ii  libx11-6  2:1.3.3-3  X11 client-side library

ht recommends no packages.

ht suggests no packages.

-- 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#453408: is this bug same as #155835?

2007-11-30 Thread Yasushi SHOJI
First of all, thank you for aknowledge my bug report.

I've checked b.d.o and noticed that the bug report is merged to
bug #155835.  so I've read the log and it seems that bug #155835 is
about c99 and gnu extension conflict.

as I said in the previous message, I just want to use gnu extension
version of %as, not c99. and it works if the given buffer is not
empty.  but dies with empty string, like ''.

so I thought that it is a bug in the gnu extension side.

I know you guys understand glibc much better than I do. so this not
questioning what you guys are doing, but rather I'd like to have some
explanation why #453408 and #155835 are merged, if possible. so if
someone like me checked the log will understand why.

Thank you for your time.
-- 
  yashi



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#453408: libc6: sscanf dies on an empty string if %as is used

2007-11-29 Thread Yasushi SHOJI
Package: libc6
Version: 2.7-2
Severity: normal

the following code can show you that sscanf() on empty string gets
invalid pointer if %as is used.

#include stdio.h

int main()
{
char *buf = ;
char *str;

sscanf (buf, %as, str);
printf(%s\n, str);

return 0;
}

a backtrace is below. Hope I'm not doing anything stupid.

regards,
-- 
   yashi


(gdb) r
Starting program: /tmp/a.out 
*** glibc detected *** /tmp/a.out: munmap_chunk(): invalid pointer: 
0x7fff5f9a89b0 ***
=== Backtrace: =
/usr/lib/debug/libc.so.6(cfree+0x1b6)[0x2b614b395d06]
/usr/lib/debug/libc.so.6(_IO_vfscanf+0x239f)[0x2b614b37329f]
/usr/lib/debug/libc.so.6(vsscanf+0x75)[0x2b614b383c85]
/usr/lib/debug/libc.so.6(_IO_sscanf+0x88)[0x2b614b37e8b8]
/tmp/a.out[0x40050f]
/usr/lib/debug/libc.so.6(__libc_start_main+0xf4)[0x2b614b33c1c4]
/tmp/a.out[0x400459]
=== Memory map: 
0040-00401000 r-xp  08:21 1457336
/tmp/a.out
0060-00601000 rw-p  08:21 1457336
/tmp/a.out
00601000-00622000 rw-p 00601000 00:00 0  [heap]
2b614b10-2b614b11d000 r-xp  08:21 292480 
/lib/ld-2.7.so
2b614b11d000-2b614b12 rw-p 2b614b11d000 00:00 0 
2b614b31c000-2b614b31e000 rw-p 0001c000 08:21 292480 
/lib/ld-2.7.so
2b614b31e000-2b614b472000 r-xp  08:21 23996  
/usr/lib/debug/libc-2.7.so
2b614b472000-2b614b672000 ---p 00154000 08:21 23996  
/usr/lib/debug/libc-2.7.so
2b614b672000-2b614b676000 r--p 00154000 08:21 23996  
/usr/lib/debug/libc-2.7.so
2b614b676000-2b614b677000 rw-p 00158000 08:21 23996  
/usr/lib/debug/libc-2.7.so
2b614b677000-2b614b67d000 rw-p 2b614b677000 00:00 0 
2b614b693000-2b614b6a9000 r-xp  08:21 31449  
/lib/libgcc_s.so.1
2b614b6a9000-2b614b8a8000 ---p 00016000 08:21 31449  
/lib/libgcc_s.so.1
2b614b8a8000-2b614b8a9000 rw-p 00015000 08:21 31449  
/lib/libgcc_s.so.1
7fff5f995000-7fff5f9aa000 rw-p 7fff5f995000 00:00 0  [stack]
ff60-ff601000 r-xp  00:00 0  [vdso]

Program received signal SIGABRT, Aborted.
0x2b614b34ffd5 in *__GI_raise (sig=value optimized out)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
(gdb) bt
#0  0x2b614b34ffd5 in *__GI_raise (sig=value optimized out)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1  0x2b614b351a30 in *__GI_abort () at abort.c:88
#2  0x2b614b38aa8b in __libc_message (do_abort=2, 
fmt=0x2b614b4458e8 *** glibc detected *** %s: %s: 0x%s ***\n)
at ../sysdeps/unix/sysv/linux/libc_fatal.c:170
#3  0x2b614b395d06 in *__GI___libc_free (mem=value optimized out) at 
malloc.c:5891
#4  0x2b614b37329f in _IO_vfscanf_internal (s=0x7fff5f9a8f30, format=value 
optimized out, 
argptr=0x7fff5f9a9050, errp=0x0) at vfscanf.c:2846
#5  0x2b614b383c85 in _IO_vsscanf (string=0x40060c , format=0x40060d 
%as, 
args=0x7fff5f9a9050) at iovsscanf.c:45
#6  0x2b614b37e8b8 in __sscanf (s=0x476e Address 0x476e out of bounds, 
format=0x476e Address 0x476e out of bounds) at sscanf.c:34
#7  0x0040050f in main () at scanf-bug.c:8
(gdb) 






-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.22-3-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/bash

Versions of packages libc6 depends on:
ii  libgcc1 1:4.3-20070930-1 GCC support library

libc6 recommends no packages.

-- debconf information:
  glibc/restart-failed:
  glibc/restart-services:



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#420860: xserver-xorg-core: SegFault on resize

2007-04-25 Thread Yasushi SHOJI
At Wed, 25 Apr 2007 13:17:03 +0900,
Yasushi SHOJI wrote:
 
 Package: xserver-xorg-core
 Version: 2:1.3.0.0.dfsg-2
 Severity: important
 
 I've been seeing this crash a few times a day after sid was open after
 etch's release.
 
 I'm tring to get better back trace but had an advice to report it
 anyway on #debian-x, so here goes.

got a better back trace but it seems like a fix for the problem is
already in the upstream repo.


http://gitweb.freedesktop.org/?p=mesa/mesa.git;a=commit;h=e5070bc3ca75dee31034cc543f3d2ee04e5dc032

I'm not sure I should close this bug, so I'll just leave it open.
please close this if not needed.

anyway, here is my back trace for a record.

#0  xmesa_check_and_update_buffer_size (xmctx=0x0, drawBuffer=0x24aceb0)
at xm_api.c:1887
#1  0x2b7758a9f51d in __glXMesaDrawableResize (base=value 
optimized out)
at ../../../../GL/mesa/X/xf86glx.c:113
#2  0x2b774ed35a2b in PositionWindow (pWin=0x1b3d680,
x=value optimized out, y=value optimized out)
at ../../../GL/glx/glxscreens.c:230
#3  0x00438e86 in ResizeChildrenWinSize (pWin=0x2c6bb90, dx=0, 
dy=0,
dw=0, dh=29) at ../../dix/window.c:1867
#4  0x004eb2f8 in miSlideAndSizeWindow (pWin=0x2c6bb90, x=5, 
y=173,
w=1203, h=826, pSib=0x0) at ../../mi/miwindow.c:728
#5  0x004389fc in ConfigureWindow (pWin=0x2c6bb90, mask=1,
vlist=value optimized out, client=0xc6cd00) at 
../../dix/window.c:2492
#6  0x00449796 in ProcConfigureWindow (client=0xc6cd00)
at ../../dix/dispatch.c:764
#7  0x00449f1a in Dispatch () at ../../dix/dispatch.c:457
#8  0x0043315b in main (argc=5, argv=0x7fff5d08ea18,
envp=value optimized out) at ../../dix/main.c:477

regards,
-- 
   yashi



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#419538: minicom: SEGV with deep directory

2007-04-20 Thread Yasushi SHOJI
The reason was simple.  We played with variable work_dir when we draw
the screen and left along. Then, in the next iteration, realloc() was
upset because we gave the changed wrong address as the first argument.

this is very good example why we should reduce global variables to
play with.  very nasty code.

Signed-off-by: Yasushi SHOJI [EMAIL PROTECTED]
---

Sorry to be late for such a simple fix.  I was on a bussiness trip for
a while.  anyway here is a fix.

 src/file.c |5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

Index: minicom-2.2/src/file.c
===
--- minicom-2.2.orig/src/file.c 2007-04-20 20:26:42.0 +0900
+++ minicom-2.2/src/file.c  2007-04-20 20:29:07.0 +0900
@@ -366,14 +366,15 @@
   new_dp_len = mbslen (work_dir);
   if (new_dp_len + (fmt_len = mbslen(cwd_str_fmt))  75) {
 size_t i;
+char *tmp_dir = work_dir;
 
 /* We want the last 73 characters */
 for (i = 0; 73 + i  new_dp_len + fmt_len; i++) {
   wchar_t wc;
 
-  work_dir += one_mbtowc(wc, work_dir, MB_LEN_MAX);
+  tmp_dir += one_mbtowc(wc, tmp_dir, MB_LEN_MAX);
 }
-snprintf(disp_dir, sizeof(disp_dir), ...%s, work_dir);
+snprintf(disp_dir, sizeof(disp_dir), ...%s, tmp_dir);
 snprintf(cwd_str, sizeof(cwd_str), cwd_str_fmt, disp_dir);
   } else
 snprintf(cwd_str, sizeof(cwd_str), cwd_str_fmt, work_dir);


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#419538: minicom: SEGV with deep directory

2007-04-16 Thread Yasushi SHOJI
Package: minicom
Version: 2.2-5
Severity: critical

The current minicom dies with SIGABRT when moving down to deep
directory[1].  here is a backtrace on my AMD64 but we see this on i386
too.

Please let us know if you need any additional info.

regards,
-- 
   yashi

[1] anything more than 73 char seems to trigger this bug.  In my case
I was moving down to:


/home/yashi/project/dist/atmark-dist-20060801/vendors/AtmarkTechno/Armadillo-210.Recover


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.18-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages minicom depends on:
ii  libc6 2.5-2  GNU C Library: Shared libraries
ii  libncurses5   5.5-5  Shared libraries for terminal hand

Versions of packages minicom recommends:
pn  lrzsz none (no description available)

-- no debconf information

-- back trace

Current directory is /tmp/minicom-2.2/src/
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB.  Type show warranty for details.
This GDB was configured as x86_64-linux-gnu...
Using host libthread_db library /lib/libthread_db.so.1.
(gdb) attach 15704
Attaching to program: /tmp/minicom-2.2/src/minicom, process 15704
Reading symbols from /usr/lib/debug/libc-2.5.so...done.
Loaded symbols for /usr/lib/debug/libc-2.5.so
Reading symbols from /lib/libncurses.so.5...done.
Loaded symbols for /lib/libncurses.so.5
Reading symbols from /lib/ld-linux-x86-64.so.2...Reading symbols from 
/usr/lib/debug/lib/ld-2.5.so...done.
done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Reading symbols from /lib/libdl.so.2...Reading symbols from 
/usr/lib/debug/lib/libdl-2.5.so...done.
done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /lib/libnss_compat.so.2...Reading symbols from 
/usr/lib/debug/lib/libnss_compat-2.5.so...done.
done.
Loaded symbols for /lib/libnss_compat.so.2
Reading symbols from /lib/libnsl.so.1...Reading symbols from 
/usr/lib/debug/lib/libnsl-2.5.so...done.
done.
Loaded symbols for /lib/libnsl.so.1
Reading symbols from /lib/libnss_nis.so.2...Reading symbols from 
/usr/lib/debug/lib/libnss_nis-2.5.so...done.
done.
Loaded symbols for /lib/libnss_nis.so.2
Reading symbols from /lib/libnss_files.so.2...Reading symbols from 
/usr/lib/debug/lib/libnss_files-2.5.so...done.
done.
Loaded symbols for /lib/libnss_files.so.2
0x2b5e91bf3d73 in __select_nocancel () from /usr/lib/debug/libc-2.5.so
(gdb) c
Continuing.

Program received signal SIGABRT, Aborted.
0x2b5e91b5c465 in *__GI_raise (sig=value optimized out)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
64  ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
in ../nptl/sysdeps/unix/sysv/linux/raise.c
(gdb) bt
#0  0x2b5e91b5c465 in *__GI_raise (sig=value optimized out)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1  0x2b5e91b5dc1e in *__GI_abort () at abort.c:88
#2  0x2b5e91b93b36 in __libc_message (do_abort=2, 
fmt=0x2b5e91c48b18 *** glibc detected *** %s: %s: 0x%s ***\n)
at ../sysdeps/unix/sysv/linux/libc_fatal.c:170
#3  0x2b5e91b9eb82 in *__GI___libc_realloc (oldmem=0x0, bytes=80)
at malloc.c:5758
#4  0x004193be in set_work_dir (existing=0x3d58, min_len=15704)
at file.c:254
#5  0x00419c63 in goto_filedir (
new_dir=0x575fd0 Armadillo-210.Recover, absolut=value optimized out)
at file.c:455
#6  0x0041a750 in filedir (howmany=value optimized out, 
downloading=value optimized out) at file.c:650
#7  0x0040d79d in updown (what=85, nr=value optimized out)
at updown.c:224
#8  0x00404acc in main (argc=value optimized out, 
argv=value optimized out) at minicom.c:1491
(gdb) f 4
#4  0x004193be in set_work_dir (existing=0x3d58, min_len=15704)
at file.c:254
(gdb) p existing
$1 = (void *) 0x3d58
(gdb) p (char *)existing
$2 = 0x3d58 Address 0x3d58 out of bounds
(gdb) up
#5  0x00419c63 in goto_filedir (
new_dir=0x575fd0 Armadillo-210.Recover, absolut=value optimized out)
at file.c:455
(gdb) p work_dir
$3 = 0x575b49 hi/project/dist/atmark-dist-20060801/vendors/AtmarkTechno
(gdb) 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#362547: xserver-xorg: X server crash with signal 11

2006-04-23 Thread Yasushi SHOJI
At Mon, 17 Apr 2006 10:39:21 +0900,
yashi wrote:
 
 At Sat, 15 Apr 2006 14:30:21 +0200,
 Michel Dänzer wrote:
  
  On Fri, 2006-04-14 at 12:55 +0900, Yasushi SHOJI wrote:
   Package: xserver-xorg
   Version: 6.9.0.dfsg.1-6
   Severity: critical
   
   This happend twice on my amd64 system with radeon 7200 while using
   Firefox.
   
   Backtrace:
   0: /usr/bin/X11/X(xf86SigHandler+0x8e) [0x449b3e]
   1: /lib/libc.so.6 [0x2b2bbad92e90]
   2: /lib/libc.so.6(memcpy+0x34) [0x2b2bbadd8014]
   3: /usr/X11R6/lib/modules/drivers/radeon_drv.so [0x2b2bbc7cccaf]
   4: /usr/X11R6/lib/modules/drivers/radeon_drv.so [0x2b2bbc7d055d]
   5: /usr/bin/X11/X [0x476d29]
   6: /usr/X11R6/lib/modules/extensions/libextmod.so [0x2b2bbb7808e0]
   7: /usr/bin/X11/X(Dispatch+0x197) [0x4896a7]
   8: /usr/bin/X11/X(main+0x418) [0x4967e8]
   9: /lib/libc.so.6(__libc_start_main+0xda) [0x2b2bbad7f4ca]
   10: /usr/bin/X11/X [0x430f0a]
   
   as you can see, I was not running a server with debugging symbols so
   back-trace isn't much helpful.
  
  Please install xserver-xorg-dbg and try again.
 
 Yes, that's what I'm doing right now.  but I haven't found how to
 reproduce this bug so it will take a while. I was hoping that if
 anyone else see the same symptom.

well, I couldn't reproduce this bug since I started to use -dbg
package. And now I've accidentally upgraded to newer version of X
server.  :-

so please mark this as unreproducible.

Thanks,
--
 yashi



Bug#362547: xserver-xorg: X server crash with signal 11

2006-04-16 Thread Yasushi SHOJI
Hi Michel,

At Sat, 15 Apr 2006 14:30:21 +0200,
Michel Dänzer wrote:
 
 On Fri, 2006-04-14 at 12:55 +0900, Yasushi SHOJI wrote:
  Package: xserver-xorg
  Version: 6.9.0.dfsg.1-6
  Severity: critical
  
  This happend twice on my amd64 system with radeon 7200 while using
  Firefox.
  
  Backtrace:
  0: /usr/bin/X11/X(xf86SigHandler+0x8e) [0x449b3e]
  1: /lib/libc.so.6 [0x2b2bbad92e90]
  2: /lib/libc.so.6(memcpy+0x34) [0x2b2bbadd8014]
  3: /usr/X11R6/lib/modules/drivers/radeon_drv.so [0x2b2bbc7cccaf]
  4: /usr/X11R6/lib/modules/drivers/radeon_drv.so [0x2b2bbc7d055d]
  5: /usr/bin/X11/X [0x476d29]
  6: /usr/X11R6/lib/modules/extensions/libextmod.so [0x2b2bbb7808e0]
  7: /usr/bin/X11/X(Dispatch+0x197) [0x4896a7]
  8: /usr/bin/X11/X(main+0x418) [0x4967e8]
  9: /lib/libc.so.6(__libc_start_main+0xda) [0x2b2bbad7f4ca]
  10: /usr/bin/X11/X [0x430f0a]
  
  as you can see, I was not running a server with debugging symbols so
  back-trace isn't much helpful.
 
 Please install xserver-xorg-dbg and try again.

Yes, that's what I'm doing right now.  but I haven't found how to
reproduce this bug so it will take a while. I was hoping that if
anyone else see the same symptom.

 It would also be interesting to know if this still happens with
 xf86-video-ati.

you mean xserver-xorg-video-ati? i still can't install
xserver-xorg-video-ati since some tools I'm using conflicts others.

 Last but not least, does this happen when visiting any particular
 site(s) with Firefox?

I doubt it but will see.

Thanks for you comments.
--
yashi



Bug#336666: xmltex: unmet dependencies in sid

2005-10-31 Thread Yasushi SHOJI
Package: xmltex
Severity: grave
Version: 1.9-10
Tags: sid


Hello,

It seems to me that xmltex is uninstallable in sid right now, or am I
missign something?


$ sudo apt-get install xmltex
  :
The following packages have unmet dependencies:
  xmltex: Depends: tetex-bin (= 1.0.7+20011202-5.1) but it is not going to be 
installed
  Depends: tetex-extra but it is not going to be installed
E: Broken packages



$ dpkg -l tetex-bin tetex-extra
  :
ii  tetex-bin  3.0-10.1   The teTeX binary files
ii  tetex-extra3.0-10 Additional library files of teTeX



-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14
Locale: LANG=C, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]