Bug#1060158: warzone2100: cannot connect to lobby

[Linus Lüssing]

Hi,

Can't reproduce this issue. Can only force this issue by emptying
my /etc/resolv.conf.

What are the contens and permissions of your /etc/resolv.conf?
$ cat /etc/resolv.conf; ls -lah /etc/resolv.conf

Also, do you use/have a /etc/nsswitch.conf?
($ dpkg -l | grep libnss; cat /etc/nsswitch.conf)

Regards, Linus

Bug#1076482: warzone2100: new release, update to 4.5.1?

[Linus Lüssing]

Package: warzone2100
Version: 4.4.2-1+b1
Severity: normal
X-Debbugs-Cc: linus.luess...@c0d3.blue

Dear Maintainer,

A new Warzone2100 version was released:

https://wz2100.net/news/version-4-5-1/

It would be great if the Debian package could be updated, to be able to
use the lobby again.

Regards, Linus


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

Kernel: Linux 6.9.8-amd64 (SMP w/16 CPU threads; PREEMPT)
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 warzone2100 depends on:
ii  bubblewrap  0.9.0-1
ii  libasound2t64   1.2.12-1
ii  libc6   2.38-14
ii  libcurl3t64-gnutls  8.8.0-4
ii  libdecor-0-00.2.2-1+b1
ii  libdrm2 2.4.121-2
ii  libfreetype62.13.2+dfsg-1+b4
ii  libfribidi0 1.0.13-3+b1
ii  libgbm1 24.1.3-2
ii  libgcc-s1   14.1.0-4
ii  libharfbuzz0b   8.3.0-2+b1
ii  libminiupnpc17  2.2.6-1+b1
ii  libogg0 1.3.5-3+b1
ii  libopenal1  1:1.23.1-4+b1
ii  libopus01.5.2-2
ii  libphysfs1  3.0.2-6+b1
ii  libpng16-16t64  1.6.43-5
ii  libpulse0   16.1+dfsg1-5.1
ii  libsamplerate0  0.2.2-4+b1
ii  libsodium23 1.0.18-1+b1
ii  libsqlite3-03.46.0-1
ii  libstdc++6  14.1.0-4
ii  libtheora0  1.1.1+dfsg.1-16.1+b2
ii  libvorbis0a 1.3.7-2
ii  libvorbisfile3  1.3.7-2
ii  libwayland-client0  1.22.0-2.1+b1
ii  libwayland-cursor0  1.22.0-2.1+b1
ii  libwayland-egl1 1.22.0-2.1+b1
ii  libx11-62:1.8.7-1+b1
ii  libxcursor1 1:1.2.2-1
ii  libxext62:1.3.4-1+b1
ii  libxfixes3  1:6.0.0-2+b1
ii  libxi6  2:1.8.1-1
ii  libxkbcommon0   1.6.0-1+b1
ii  libxrandr2  2:1.5.4-1
ii  libxss1 1:1.2.3-1+b1
ii  warzone2100-data4.4.2-1
ii  zlib1g  1:1.3.dfsg+really1.3.1-1

Versions of packages warzone2100 recommends:
ii  warzone2100-music  4.4.2-1

warzone2100 suggests no packages.

-- no debconf information

Bug#1076380: Acknowledgement (screen: hangs for ~10 seconds when creating tab with zsh+unlimit)

[Linus Lüssing]

Attaching an strace as well, created via:

  $ zsh -c "unlimit; strace screen 2> /tmp/screen-strace.txt"

It keeps busy looping around a poll().
execve("/usr/bin/screen", ["screen"], 0x7fffb31018a0 /* 41 vars */) = 0
brk(NULL)   = 0x5639e1ba9000
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x152dc0d42000
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=242055, ...}, AT_EMPTY_PATH) = 0
mmap(NULL, 242055, PROT_READ, MAP_PRIVATE, 3, 0) = 0x152dc0d06000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libtinfo.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 
832) = 832
newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=216368, ...}, AT_EMPTY_PATH) = 0
mmap(NULL, 215360, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x152dc0cd1000
mmap(0x152dc0ce, 77824, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xf000) = 0x152dc0ce
mmap(0x152dc0cf3000, 57344, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x22000) = 0x152dc0cf3000
mmap(0x152dc0d01000, 20480, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3) = 0x152dc0d01000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libutempter.so.0", O_RDONLY|O_CLOEXEC) 
= 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 
832) = 832
newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=14256, ...}, AT_EMPTY_PATH) = 0
mmap(NULL, 16416, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x152dc0ccc000
mmap(0x152dc0ccd000, 4096, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1000) = 0x152dc0ccd000
mmap(0x152dc0cce000, 4096, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x2000) = 0x152dc0cce000
mmap(0x152dc0ccf000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2000) = 0x152dc0ccf000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libcrypt.so.1", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 
832) = 832
newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=206776, ...}, AT_EMPTY_PATH) = 0
mmap(NULL, 242344, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x152dc0c9
mmap(0x152dc0c92000, 90112, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2000) = 0x152dc0c92000
mmap(0x152dc0ca8000, 106496, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x18000) = 0x152dc0ca8000
mmap(0x152dc0cc2000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x31000) = 0x152dc0cc2000
mmap(0x152dc0cc4000, 29352, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x152dc0cc4000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libpam.so.0", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 
832) = 832
newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=67584, ...}, AT_EMPTY_PATH) = 0
mmap(NULL, 69648, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x152dc0c7e000
mmap(0x152dc0c81000, 36864, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3000) = 0x152dc0c81000
mmap(0x152dc0c8a000, 16384, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0xc000) = 0x152dc0c8a000
mmap(0x152dc0c8e000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xf000) = 0x152dc0c8e000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P~\2\0\0\0\0\0"..., 832) 
= 832
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 
784, 64) = 784
newfstatat(3, "", {st_mode=S_IFREG|0755, st_size=1933688, ...}, AT_EMPTY_PATH) 
= 0
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 
784, 64) = 784
mmap(NULL, 1985936, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x152dc0a99000
mmap(0x152dc0abf000, 1404928, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x26000) = 0x152dc0abf000
mmap(0x152dc0c16000, 348160, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x17d000) = 0x152dc0c16000
mmap(0x152dc0c6b000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1d1000) = 0x152dc0c6b000
mmap(0x152dc0c71000, 52624, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x152dc0c71000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libaudit.so.1", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 
832) = 832
newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=137144, ...}, AT_EMPTY_PATH) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 

Bug#1069303: dia: Cisco - Network: Cloud* does not draw outline on SVG export

[Linus Lüssing]

Package: dia
Version: 0.98+git20240130-1+b1
Severity: normal
X-Debbugs-Cc: linus.luess...@c0d3.blue

Dear Maintainer,

When I try to export an image involving a cloud from the "Cisco - Network"
category to SVG then its outline is not drawn.

When then converting for instance a "Cloud White" from SVG to PNG
(for instance via the ImageMagick "convert" CLI tool) then the cloud
vanishes completely, due to the missing outline.

Regards, Linus

*** 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: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 dia depends on:
ii  dia-common   0.98+git20240130-1
ii  gir1.2-gtk-3.0   3.24.41-4
ii  libc62.37-15.1
ii  libcairo21.18.0-3
ii  libemf1  1.0.13-7
ii  libgcc-s114-20240315-1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-3+b2
ii  libglib2.0-0t64  2.78.4-6
ii  libgraphene-1.0-01.10.8-3+b1
ii  libgtk-3-0t643.24.41-4
ii  libpango-1.0-0   1.52.1+ds-1
ii  libpangocairo-1.0-0  1.52.1+ds-1
ii  libpoppler126t64 22.12.0-2.2
ii  libpython3.11t64 3.11.8-3+b2
ii  libstdc++6   14-20240315-1
ii  libxml2  2.9.14+dfsg-1.3+b2
ii  zlib1g   1:1.3.dfsg-3.1

Versions of packages dia recommends:
ii  dia-shapes0.6.0-5
ii  fonts-urw-base35  20200910-8

dia suggests no packages.

-- no debconf information

Bug#1065360: libopencv-dev: dependency issues, can't install

[Linus Lüssing]

Ok, while apt-get wasn't able to resolve the dependencies,
aptitude was to able to find a solution to simply install
libopencv-dev and this seems to confirm that it's an issue with the
time_t migration, I think?

```
Start-Date: 2024-03-03  16:13:08
Requested-By: user (1000)
Install: libevent-pthreads-2.1-7:amd64 (2.1.12-stable-8, automatic), 
libgl2ps1.4:amd64 (1.4.2+dfsg1-2, automatic), libcharls2:amd64 (2.4.2-2+b1, 
automatic), libexif-dev:amd64 (0.6.24-1+b1, automatic), python3.12:amd64 
(3.12.2-4, automatic), libgeotiff5:amd64 (1.7.1-5, automatic), 
liburiparser1:amd64 (0.9.7+dfsg-2+b1, automatic), libgdal34t64:amd64 
(3.8.4+dfsg-3, automatic), libopencv-shape406t64:amd64 (4.6.0+dfsg-13.1, 
automatic), libamd-comgr2:amd64 (6.0+git20231212.4510c28+dfsg-3, automatic), 
libtesseract5:amd64 (5.3.4-1, automatic), libopencv-videoio-dev:amd64 
(4.6.0+dfsg-13.1, automatic), libopencv-objdetect-dev:amd64 (4.6.0+dfsg-13.1, 
automatic), librdmacm1t64:amd64 (50.0-2, automatic), libxerces-c3.2t64:amd64 
(3.2.4+debian-1.2, automatic), gdal-plugins:amd64 (3.8.4+dfsg-3, automatic), 
libopencv-superres-dev:amd64 (4.6.0+dfsg-13.1, automatic), libaec0:amd64 
(1.1.2-1, automatic), libarmadillo12:amd64 (1:12.6.7+dfsg-1, automatic), 
libopencv-contrib-dev:amd64 (4.6.0+dfsg-13.1, automatic), opencv-data:amd64 
(4.6.0+dfsg-13.1, automatic), libmunge2:amd64 (0.5.15-3+b1, automatic), 
libpoppler-cpp0t64:amd64 (22.12.0-2.2, automatic), libwebpdecoder3:amd64 
(1.3.2-0.4, automatic), libamdhip64-5:amd64 (5.2.3-13, automatic), 
libopencv-features2d406t64:amd64 (4.6.0+dfsg-13.1, automatic), 
libpoppler126t64:amd64 (22.12.0-2.2, automatic), libibverbs1:amd64 (50.0-2, 
automatic), libwebp-dev:amd64 (1.3.2-0.4, automatic), 
libopencv-imgcodecs-dev:amd64 (4.6.0+dfsg-13.1, automatic), mysql-common:amd64 
(5.8+1.1.0, automatic), libpython3.12-minimal:amd64 (3.12.2-4, automatic), 
libopencv-imgcodecs406t64:amd64 (4.6.0+dfsg-13.1, automatic), 
libnetcdf19t64:amd64 (1:4.9.2-5, automatic), liblerc-dev:amd64 (4.0.0+ds-4+b1, 
automatic), libtiffxx6:amd64 (4.5.1+git230720-4, automatic), 
libopencv-video406t64:amd64 (4.6.0+dfsg-13.1, automatic), libfreexl1:amd64 
(2.0.0-1+b1, automatic), libopenexr-dev:amd64 (3.1.5-5.1+b1, automatic), 
libsuperlu6:amd64 (6.0.1+dfsg1-1+b1, automatic), libtcl8.6:amd64 
(8.6.14+dfsg-1, automatic), libopencv-objdetect406t64:amd64 (4.6.0+dfsg-13.1, 
automatic), libminizip1t64:amd64 (1:1.3.dfsg-3.1, automatic), 
libkmldom1t64:amd64 (1.3.0-12, automatic), libopencv-video-dev:amd64 
(4.6.0+dfsg-13.1, automatic), liblept5:amd64 (1.82.0-3+b3, automatic), 
libjbig-dev:amd64 (2.1-6.1+b1, automatic), libgphoto2-dev:amd64 (2.5.31-2.1, 
automatic), libopencv-shape-dev:amd64 (4.6.0+dfsg-13.1, automatic), 
libtk8.6:amd64 (8.6.14-1, automatic), libopencv-calib3d406t64:amd64 
(4.6.0+dfsg-13.1, automatic), libopencv-photo406t64:amd64 (4.6.0+dfsg-13.1, 
automatic), libopencv-highgui406t64:amd64 (4.6.0+dfsg-13.1, automatic), 
libopencv-core406t64:amd64 (4.6.0+dfsg-13.1, automatic), libproj25:amd64 
(9.4.0-1, automatic), libcfitsio10t64:amd64 (4.3.1-1.1, automatic), 
libnettle8t64:amd64 (3.9.1-2.1, automatic), libnettle8t64:i386 (3.9.1-2.1, 
automatic), libarpack2t64:amd64 (3.9.1-1.1, automatic), libsocket++1:amd64 
(1.12.13+git20131030.5d039ba-1+b1, automatic), libraw1394-tools:i386 (2.1.2-2, 
automatic), libcurl3t64-gnutls:amd64 (8.6.0-3.2, automatic), 
libcurl3t64-gnutls:i386 (8.6.0-3.2, automatic), libkmlbase1t64:amd64 (1.3.0-12, 
automatic), libimath-dev:amd64 (3.1.9-3.1, automatic), 
libopencv-highgui-dev:amd64 (4.6.0+dfsg-13.1, automatic), liblzma-dev:amd64 
(5.6.0-0.2, automatic), libdc1394-dev:amd64 (2.2.6-4, automatic), 
libopencv-core-dev:amd64 (4.6.0+dfsg-13.1, automatic), librttopo1:amd64 
(1.1.0-3, automatic), libswscale-dev:amd64 (7:6.1.1-2, automatic), 
libopencv-stitching-dev:amd64 (4.6.0+dfsg-13.1, automatic), 
libhdf5-103-1t64:amd64 (1.10.10+repack-3.1, automatic), 
libopencv-stitching406t64:amd64 (4.6.0+dfsg-13.1, automatic), 
libdeflate-dev:amd64 (1.19-1, automatic), libopencv-ml406t64:amd64 
(4.6.0+dfsg-13.1, automatic), python3-numpy:amd64 (1:1.24.2-2, automatic), 
libopencv-videoio406t64:amd64 (4.6.0+dfsg-13.1, automatic), 
libopencv-contrib406t64:amd64 (4.6.0+dfsg-13.1, automatic), libodbcinst2:amd64 
(2.3.12-1+b1, automatic), libqhull-r8.0:amd64 (2020.2-6+b1, automatic), 
libblosc1:amd64 (1.21.5+ds-1+b1, automatic), libkmlengine1t64:amd64 (1.3.0-12, 
automatic), libhsakmt1:amd64 (5.7.0-1, automatic), 
libopencv-imgproc406t64:amd64 (4.6.0+dfsg-13.1, automatic), libzstd-dev:amd64 
(1.5.5+dfsg2-2, automatic), mariadb-common:amd64 (1:10.11.7-2, automatic), 
libspatialite8t64:amd64 (5.1.0-3, automatic), libfabric1:amd64 (1.17.0-3, 
automatic), libgeos3.12.1t64:amd64 (3.12.1-3, automatic), 
libopencv-dnn406t64:amd64 (4.6.0+dfsg-13.1, automatic), ibverbs-providers:amd64 
(50.0-2, automatic), libgdcm-dev:amd64 (3.0.22-2.1, automatic), 
libopencv-viz-dev:amd64 (4.6.0+dfsg-13.1, automatic), libgdcm3.0t64:amd64 

Bug#1065360: libopencv-dev: dependency issues, can't install

[Linus Lüssing]

Package: libopencv-dev
Severity: important

Dear Maintainer,

I'm currently getting the following error:

```
$ sudo apt-get install libopencv-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 glib-networking:i386 : Depends: libgnutls30:i386 (>= 3.8.1)
Depends: libproxy1v5:i386 (>= 0.5.3) but it is not 
going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.
```

I'm wondering if that might be related to the current time_t 64bit
transition in Debian?

I'm probably having some library which I should have the *t64 variant
of, as I have i386 installed as a foreign arch for wine here.

However, "apt-get update && apt-get dist-upgrade" currently does not
show any todos.

Regards, Linus


*** 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: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.6.15-amd64 (SMP w/4 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 libopencv-dev depends on:
ii  libc6   2.37-15.1
ii  libgcc-s1   14-20240221-2.1
pn  libilmbase-dev  
pn  libopencv-calib3d-dev   
pn  libopencv-calib3d406t64 
pn  libopencv-contrib-dev   
pn  libopencv-contrib406t64 
pn  libopencv-core-dev  
pn  libopencv-core406t64
pn  libopencv-dnn-dev   
pn  libopencv-dnn406t64 
pn  libopencv-features2d-dev
pn  libopencv-features2d406t64  
pn  libopencv-flann-dev 
pn  libopencv-highgui-dev   
pn  libopencv-highgui406t64 
pn  libopencv-imgcodecs-dev 
pn  libopencv-imgcodecs406t64   
pn  libopencv-imgproc-dev   
pn  libopencv-imgproc406t64 
pn  libopencv-ml-dev
pn  libopencv-objdetect-dev 
pn  libopencv-photo-dev 
pn  libopencv-shape-dev 
pn  libopencv-stitching-dev 
pn  libopencv-superres-dev  
pn  libopencv-video-dev 
pn  libopencv-videoio-dev   
pn  libopencv-videoio406t64 
pn  libopencv-videostab-dev 
pn  libopencv-viz-dev   
ii  libstdc++6  14-20240221-2.1
ii  pkg-config  1.8.1-1+b2
ii  pkgconf [pkg-config]1.8.1-1+b2

Versions of packages libopencv-dev recommends:
pn  libopencv-java  
pn  opencv-data 

Versions of packages libopencv-dev suggests:
pn  opencv-doc  

Bug#1065336: lxpanel: Depends: libfm-modules but is not installable

[Linus Lüssing]

Package: lxpanel
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: linus.luess...@c0d3.blue

Dear Maintainer,

On a Debian Sid system with "task-lxqt-desktop" and "task-lxde-desktop" 
installed
an "apt-get dist-upgrade" has removed these packages and by that a large
list of other packages and made a login into a graphical desktop /
window manager impossible.

Trying to reinstall "task-lxde-desktop" results in the following error:

```
The following packages have unmet dependencies:
 lxpanel : Depends: libfm-modules but ist is not installable
```

Or trying to reinstall "task-lxqt-desktop" results in:

```
The following packages have unmet dependencies:
 libfm-qt13 : Depends: libglib2.0-bin
 libqt5xdg3 : Depends: libglib2.0-bin
```

Manually running "apt-get install libfm-modules" ran through fine,
removed "libfm-extra4" automatically and by that fixed the "task-lxde-desktop" /
"lxpanel" installation for me. After that I could run "apt-get install
task-lxde-desktop" without any issues.

For "task-lxqt-desktop" I couldn't quite figure out a solution yet (but
is likely unrelated to lxpanel / libfm dependencies anyway, I guess).

Regards, Linus


*** 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: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 6.6.11-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 lxpanel depends on:
ii  libasound2   1.2.10-3
ii  libc62.37-13
ii  libcairo21.18.0-1+b1
ii  libcurl3-gnutls  8.5.0-2
pn  libfm-gtk3-4 
pn  libfm-modules
pn  libfm4   
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-3+b1
ii  libglib2.0-0 2.78.3-1
ii  libgtk-3-0   3.24.41-1
ii  libiw30  30~pre9-16+b1
pn  libkeybinder-3.0-0   
pn  libmenu-cache3   
ii  libpango-1.0-0   1.51.0+ds-4
ii  libwnck-3-0  43.0-3
ii  libx11-6 2:1.8.7-1
ii  libxml2  2.9.14+dfsg-1.3+b2
pn  lxmenu-data  
pn  lxpanel-data 

Versions of packages lxpanel recommends:
ii  awesome [notification-daemon]   4.3-7
ii  dunst [notification-daemon] 1.9.2-1
ii  gnome-shell [notification-daemon]   44.7-1
ii  gnome-terminal [x-terminal-emulator]3.50.1-1
ii  libnotify-bin   0.8.3-1
ii  lxterminal [x-terminal-emulator]0.4.0-2
ii  notification-daemon 3.20.0-4+b1
ii  pavucontrol 5.0-2
ii  plasma-workspace [notification-daemon]  4:5.27.10-2
ii  xkb-data2.38-2
ii  xterm [x-terminal-emulator] 389-1

Versions of packages lxpanel suggests:
ii  chromium [www-browser]  120.0.6099.199-1
ii  firefox [www-browser]   121.0-2
ii  lynx [www-browser]  2.9.0dev.12-1

Bug#1059384: ipv6calc: IPv6 link-local multicast with transient flag not detected as ll

[Linus Lüssing]

Package: ipv6calc
Version: 4.1.0-0.1
Severity: normal
X-Debbugs-Cc: linus.luess...@c0d3.blue

Dear Maintainer,

With the following I'm getting the "Address type" as expected:

```
$ echo "ff02::123" | ipv6calc -i
Address type: multicast, link-local
Registry for address: reserved(RFC4291#2.7)
Interface identifier: :::0123
Interface identifier is probably manual set
```

However when setting the transient flag then ipv6calc is not able to
detect it as link-local anymore:

```
$ echo "ff12::123" | ipv6calc -i
Address type: multicast
Registry for address: reserved(RFC4291#2.7)
```

I would have expected an "Address type" with "link-local" in the second
example, similar to the output of the first command

Regards, Linus

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

Kernel: Linux 6.5.0-4-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 ipv6calc depends on:
ii  libc6  2.37-12
ii  libmaxminddb0  1.8.0-1

ipv6calc recommends no packages.

Versions of packages ipv6calc suggests:
ii  bind9-host [host]  1:9.19.17-1

-- no debconf information

Bug#1033828: mono-xbuild: Mono packages should provide msbuild instead of xbuild

[Linus Lüssing]

Package: mono-devel
Version: 6.8.0.105+dfsg-3.3
Followup-For: Bug #1033828
X-Debbugs-Cc: linus.luess...@c0d3.blue

Hi,

Just wanted to add that trying to build OpenRA currently fails with the
following error for me:

```
$ make RUNTIME=mono
Compiling in Release mode...
OpenRA requires the 'msbuild -verbosity:m -nologo' tool provided by Mono >= 
6.12.
make: *** [Makefile:94: all] Error 1
make RUNTIME=mono  0.00s user 0.01s system 96% cpu 0.017 total
```

Its INSTALL.md suggests to update and install mono from the mono
project's Debian package repository:

https://github.com/OpenRA/OpenRA/blob/bleed/INSTALL.md#linux

It would be great if mono could be updated to 6.12 and could add
"msbuild" in Debian directly to hopefully fix this issue, without
needing to resort to an alternative package repository.

Regards, Linus


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

Kernel: Linux 6.4.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 mono-devel depends on:
ii  ca-certificates-mono  6.8.0.105+dfsg-3.3
ii  libc6 2.37-6
ii  libmono-2.0-dev   6.8.0.105+dfsg-3.3
ii  libmono-cecil-private-cil 6.8.0.105+dfsg-3.3
ii  libmono-cil-dev   6.8.0.105+dfsg-3.3
ii  libmono-codecontracts4.0-cil  6.8.0.105+dfsg-3.3
ii  libmono-compilerservices-symbolwriter4.0-cil  6.8.0.105+dfsg-3.3
ii  libmono-corlib4.5-cil 6.8.0.105+dfsg-3.3
ii  libmono-peapi4.0a-cil 6.8.0.105+dfsg-3.3
ii  libmono-relaxng4.0-cil6.8.0.105+dfsg-3.3
ii  libmono-security4.0-cil   6.8.0.105+dfsg-3.3
ii  libmono-system-componentmodel-composition4.0-cil  6.8.0.105+dfsg-3.3
ii  libmono-system-componentmodel-dataannotations4.0-cil  6.8.0.105+dfsg-3.3
ii  libmono-system-configuration-install4.0-cil   6.8.0.105+dfsg-3.3
ii  libmono-system-configuration4.0-cil   6.8.0.105+dfsg-3.3
ii  libmono-system-core4.0-cil6.8.0.105+dfsg-3.3
ii  libmono-system-data-datasetextensions4.0-cil  6.8.0.105+dfsg-3.3
ii  libmono-system-data4.0-cil6.8.0.105+dfsg-3.3
ii  libmono-system-drawing4.0-cil 6.8.0.105+dfsg-3.3
ii  libmono-system-identitymodel4.0-cil   6.8.0.105+dfsg-3.3
ii  libmono-system-io-compression-filesystem4.0-cil   6.8.0.105+dfsg-3.3
ii  libmono-system-io-compression4.0-cil  6.8.0.105+dfsg-3.3
ii  libmono-system-net-http4.0-cil6.8.0.105+dfsg-3.3
ii  libmono-system-numerics4.0-cil6.8.0.105+dfsg-3.3
ii  libmono-system-runtime-serialization4.0-cil   6.8.0.105+dfsg-3.3
ii  libmono-system-runtime4.0-cil 6.8.0.105+dfsg-3.3
ii  libmono-system-security4.0-cil6.8.0.105+dfsg-3.3
ii  libmono-system-servicemodel4.0a-cil   6.8.0.105+dfsg-3.3
ii  libmono-system-serviceprocess4.0-cil  6.8.0.105+dfsg-3.3
ii  libmono-system-transactions4.0-cil6.8.0.105+dfsg-3.3
ii  libmono-system-web-services4.0-cil6.8.0.105+dfsg-3.3
ii  libmono-system-web4.0-cil 6.8.0.105+dfsg-3.3
ii  libmono-system-xml-linq4.0-cil6.8.0.105+dfsg-3.3
ii  libmono-system-xml4.0-cil 6.8.0.105+dfsg-3.3
ii  libmono-system4.0-cil 6.8.0.105+dfsg-3.3
ii  mono-gac  6.8.0.105+dfsg-3.3
ii  mono-mcs  6.8.0.105+dfsg-3.3
ii  mono-runtime  6.8.0.105+dfsg-3.3
ii  mono-xbuild   6.8.0.105+dfsg-3.3
ii  pkg-config1.8.1-1
ii  pkgconf [pkg-config]  1.8.1-1

Versions of packages mono-devel recommends:
ii  mono-csharp-shell  6.8.0.105+dfsg-3.3

mono-devel suggests no packages.

-- no debconf information

Bug#1043351: ebtables: unescaped hyphens in manpage

[Linus Lüssing]

Package: ebtables
Version: 2.0.11-5
Severity: normal
X-Debbugs-Cc: linus.luess...@c0d3.blue

Dear Maintainer,

I tried running the following ebtables command, but got an error:

```
$ sudo ebtables -I INPUT -i veth1 -j mark ‐‐mark-set 0x42
ebtables v1.8.9 (nf_tables): Bad argument : '‐‐mark-set'
```

On #netfilter IRC people with eagle-eyes and apparently a different font
than me pointed out that I was trying to use Unicode instead of ASCII
hyphens. Changing the command to use "--mark-set", with ASCII hyphens,
instead helped.

It seems I copied the Unicode version from the ebtables manpage. I believe
it's a similar issue to this one:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043309

That is un-escaped hyphens in the manpage source code are rendered to
Unicode hyphens.

To fix this the hyphens should be escaped in the manpage source code.

Regards, Linus

(Kudos to @aiyion@infosec.exchange on Mastodon who pointed me to the
curl Debian bug report and by that to the origin of my issue.)


*** 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: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 6.4.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 ebtables depends on:
ii  libc62.37-6
ii  netbase  6.4

Versions of packages ebtables recommends:
ii  iptables  1.8.9-2
ii  kmod  30+20230519-1

ebtables suggests no packages.

-- no debconf information

Bug#1037028: warzone2100: Update to version 4.3.5, to enable multiplayer again

[Linus Lüssing]

Package: warzone2100
Version: 4.3.3-3
Severity: normal
X-Debbugs-Cc: linus.luess...@c0d3.blue

Hi,

There've been two more releases, the latest version now is 4.3.5. It
would be great if the package could be updated accordingly to allow
joining multiplayer games again.

Regards, Linus


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

Kernel: Linux 6.1.0-6-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 warzone2100 depends on:
ii  libasound2  1.2.8-1+b1
ii  libc6   2.36-9
ii  libcurl3-gnutls 7.88.1-9
ii  libdecor-0-00.1.1-2
ii  libdrm2 2.4.114-1+b1
ii  libfreetype62.12.1+dfsg-5
ii  libfribidi0 1.0.8-2.1
ii  libgbm1 23.1.0-1
ii  libgcc-s1   12.2.0-14
ii  libharfbuzz0b   6.0.0+dfsg-3
ii  libminiupnpc17  2.2.4-1+b1
ii  libogg0 1.3.5-3
ii  libopenal1  1:1.19.1-2
ii  libopus01.3.1-3
ii  libphysfs1  3.0.2-6
ii  libpng16-16 1.6.39-2
ii  libpulse0   16.1+dfsg1-2+b1
ii  libsamplerate0  0.2.2-3
ii  libsodium23 1.0.18-1
ii  libsqlite3-03.40.1-2
ii  libstdc++6  12.2.0-14
ii  libtheora0  1.1.1+dfsg.1-16.1+b1
ii  libvorbis0a 1.3.7-1
ii  libvorbisfile3  1.3.7-1
ii  libwayland-client0  1.21.0-1
ii  libwayland-cursor0  1.21.0-1
ii  libwayland-egl1 1.21.0-1
ii  libx11-62:1.8.4-2
ii  libxcursor1 1:1.2.1-1
ii  libxext62:1.3.4-1+b1
ii  libxfixes3  1:6.0.0-2
ii  libxi6  2:1.8-1+b1
ii  libxkbcommon0   1.5.0-1
ii  libxrandr2  2:1.5.2-2+b1
ii  libxss1 1:1.2.3-1
ii  warzone2100-data4.3.3-3
ii  zlib1g  1:1.2.13.dfsg-1

Versions of packages warzone2100 recommends:
ii  warzone2100-music  4.3.3-3

warzone2100 suggests no packages.

-- no debconf information

Bug#1028549: Acknowledgement (xserver-xorg-video-radeon: [Radeon 680M]: not rendering/refreshing fullscreen properly with VSync off)

[Linus Lüssing]

Just for a small update:

Issue still persists, even with all packages updated to a current
Debian Sid (including adding the new "non-free-firmware" section
to apt).

ii  xserver-xorg-video-radeon1:19.1.0-3
ii  libc6:amd64  2.36-8
ii  libc6:i386   2.36-8
ii  libdrm-radeon1:amd64 2.4.114-1
ii  libdrm-radeon1:i386  2.4.114-1
ii  libgbm1:amd6422.3.6-1
ii  libgbm1:i386 22.3.6-1
ii  libudev1:i386252.6-1
ii  xserver-xorg-core2:21.1.7-1
ii  firmware-amd-graphics20230210-2

$ uname -a
Linux linus-lptp 6.1.0-5-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.12-1 
(2023-02-15) x86_64 GNU/Linux

Regards, Linus

Bug#1031655: Lutris: "The wine build you have selected does not support Esync/Fsync"

[Linus Lüssing]

Package: wine
Version: 8.0~repack-4
Severity: wishlist
X-Debbugs-Cc: linus.luess...@c0d3.blue

Dear Maintainer,

When I select "System (8.0 (Debian 8.0~repack-4))" in Lutris under a
game's "Runner option" and then trying to select "Enable Esync" or
"Enable Fsync" in that same menu I get the following error message:

  Incompatible Wine version detected
  The Wine build you have selected does not support Esync.
  Please switch to a Esync-capable version.

or:

  Incompatible Wine version detected
  The Wine build you have selected does not support Fsync
  Please switch to a Fsync-capable version.

According to its mouse-over description they are there to increase
multi-threaded performance. They sound like build options to me and work
with the following other runners for me: lutris-mtga-5.0-x86_64 or
lutris-GE-Proton7-35-x86_64.

Would it make sense to somehow enable these options in Debian's wine
version, too? (Or are they non-sense options? I haven't verified their
performance boost claims.)

Regards, Linus


*** 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 ***


-- Package-specific info:
/usr/bin/wine points to /usr/bin/wine-stable.

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

Kernel: Linux 6.1.0-5-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 wine depends on:
ii  wine32  8.0~repack-4
ii  wine64  8.0~repack-4

wine recommends no packages.

Versions of packages wine suggests:
ii  dosbox   0.74-3-4+b1
ii  kio-extras   4:22.12.2-1
pn  playonlinux  
pn  q4wine   
pn  winbind  
pn  wine-binfmt  
ii  winetricks   20220411-1

Versions of packages libwine depends on:
ii  libasound2   1.2.8-1+b1
ii  libc62.36-8
ii  libcapi20-3  1:3.27-3+b1
ii  libfontconfig1   2.14.1-4
ii  libfreetype6 2.12.1+dfsg-4
ii  libglib2.0-0 2.74.5-1
ii  libgphoto2-6 2.5.30-1
ii  libgphoto2-port122.5.30-1
ii  libgstreamer-plugins-base1.0-0   1.22.0-3
ii  libgstreamer1.0-01.22.0-2
ii  libpcap0.8   1.10.3-1
ii  libpulse016.1+dfsg1-2+b1
ii  libudev1 252.5-2
ii  libunwind8   1.6.2-3
ii  libusb-1.0-0 2:1.0.26-1
ii  libx11-6 2:1.8.3-3
ii  libxext6 2:1.3.4-1+b1
ii  libz-mingw-w64   1.2.13+dfsg-1
ii  ocl-icd-libopencl1 [libopencl1]  2.3.1-1

Versions of packages libwine recommends:
ii  fonts-liberation   1:1.07.4-11
ii  fonts-wine 8.0~repack-4
ii  gstreamer1.0-plugins-good  1.22.0-4
ii  libasound2-plugins 1.2.7.1-1
ii  libcups2   2.4.2-1+b2
ii  libdbus-1-31.14.6-1
ii  libgl1 1.6.0-1
ii  libgl1-mesa-dri22.3.5-1
ii  libgnutls303.7.9-1
ii  libgssapi-krb5-2   1.20.1-1
ii  libkrb5-3  1.20.1-1
ii  libodbc2   2.3.11-2
ii  libosmesa6 22.3.5-1
ii  libsdl2-2.0-0  2.26.3+dfsg-1
ii  libv4l-0   1.22.1-5+b1
ii  libvulkan1 1.3.239.0-1
ii  libxcomposite1 1:0.4.5-1
ii  libxcursor11:1.2.1-1
ii  libxfixes3 1:6.0.0-2
ii  libxi6 2:1.8-1+b1
ii  libxinerama1   2:1.1.4-3
ii  libxrandr2 2:1.5.2-2+b1
ii  libxrender11:0.9.10-1.1
ii  libxxf86vm11:1.1.4-1+b2

Versions of packages libwine suggests:
ii  cups-bsd   2.4.2-1+b2
ii  gstreamer1.0-libav 1.22.0-2
ii  gstreamer1.0-plugins-bad   1.22.0-3
ii  gstreamer1.0-plugins-ugly  1.22.0-2
pn  ttf-mscorefonts-installer  

Versions of packages wine32 depends on:
ii  libc62.36-8
ii  libwine  8.0~repack-4

wine32 recommends no packages.

Versions of packages wine32 suggests:
pn  wine32-preloader  

Versions of packages wine64 depends on:
ii  libc62.36-8
ii  libwine  8.0~repack-4

Versions of packages wine64 recommends:
ii  wine32  8.0~repack-4

Versions of packages wine64 suggests:
pn  wine64-preloader  

Versions of packages wine is related to:
pn  dxvk 
pn  dxvk-wine32-development  
pn  dxvk-wine64-development  
ii  fonts-wine   8.0~repack-4

-- no debconf information

Bug#1029199: taskell: Depends: libffi7 (>= 3.3~20180313) but it is not installable

[Linus Lüssing]

Package: taskell
Version: 1.4.0.0-1
Severity: important
X-Debbugs-Cc: linus.luess...@c0d3.blue

Dear Maintainer,

It seems that an update changed libffi7 to libffi8. libffi7 is not
available on Debian Sid anymore and trying to install taskell results in
the following error:

  $ apt-get install taskell
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
   taskell : Depends: libffi7 (>= 3.3~20180313) but it is not installable
  E: Unable to correct problems, you have held broken packages.

Regards, Linus

*** 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: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 6.1.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 taskell depends on:
ii  libatomic1  12.2.0-14
ii  libc6   2.36-8
pn  libffi7 
ii  libgmp102:6.2.1+dfsg1-1.1
ii  libtinfo6   6.4-1
ii  zlib1g  1:1.2.13.dfsg-1

taskell recommends no packages.

taskell suggests no packages.

Bug#1029160: pwmconfig: hangs indefintely if "no correlation" for FAN<->PWM on "minimum PWM value" test

[Linus Lüssing]

Package: fancontrol
Version: 1:3.6.0-7.1
Severity: normal
X-Debbugs-Cc: linus.luess...@c0d3.blue

Dear Maintainer,

If pwmconfig detects "no correlation" between the configured pwm1
speed and the resulting output value in fan1_input in my case (due to
the too low DELAY value, as reported in another ticket) and if I then
choose to perform the auto-detection for the "minimum PWM value" then
this hangs indefinitly on:

```
function TestMinStop()
{
[...]
fanspeed=$(cat $faninput)
```

Because $faninput is an empty string. See more detailed output below.

Regards, Linus





*** 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: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 6.1.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 fancontrol depends on:
ii  init-system-helpers1.65.2
ii  sysvinit-utils [lsb-base]  3.06-2

fancontrol recommends no packages.

fancontrol suggests no packages.

-- no debconf information


```
$ sudo pwmconfig
# pwmconfig version 3.6.0
This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.

We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.

Found the following devices:
   hwmon0 is acpitz
   hwmon1 is BAT0
   hwmon2 is nvme
   hwmon3 is amdgpu
   hwmon4 is AC
   hwmon5 is k10temp
   hwmon6 is thinkpad
   hwmon7 is ath11k_hwmon

Found the following PWM controls:
   hwmon6/pwm1   current value: 0

Giving the fans some time to reach full speed...
Found the following fan sensors:
   hwmon6/fan1_input current speed: 4926 RPM

Warning!!! This program will stop your fans, one at a time,
for approximately 5 seconds each!!!
This may cause your processor temperature to rise!!!
If you do not want to do this hit control-C now!!!
Hit return to continue: 

Testing pwm control hwmon6/pwm1 ...
~~~ i: hwmon6/pwm1, calling: pwmset hwmon6/pwm1 0 (fan1_input: 65535, pwm1: 255)
~~~ i: hwmon6/pwm1, after calling: pwmset hwmon6/pwm1 0 (fan1_input: 65535, 0)
~~~ i: hwmon6/pwm1, after calling: pwmset hwmon6/pwm1 0; sleep 5 (fan1_input: 
4918, 0)
~~~ CURRENT_SPEED: 4918, SPEEDS: 4926
~~~ j in GOODFAN: hwmon6/fan1_input in hwmon6/fan1_input
  hwmon6/fan1_input ... speed was 4926 now 4918
~~~ S: 4918, threshold: 3694, OS: 4926
no correlation

No correlations were detected.
There is either no fan connected to the output of hwmon6/pwm1,
or the connected fan has no rpm-signal connected to one of
the tested fan sensors. (Note: not all motherboards have
the pwm outputs connected to the fan connectors,
check out the hardware database on http://www.almico.com/forumindex.php)

Did you see/hear a fan stopping during the above test (n)? y

Testing is complete.
Please verify that all fans have returned to their normal speed.

The fancontrol script can automatically respond to temperature changes
of your system by changing fanspeeds.
Do you want to set up its configuration file now (y)? y
What should be the path to your fancontrol config file (/etc/fancontrol)? 
Loading configuration from /etc/fancontrol ...

Select fan output to configure, or other action:
1) hwmon6/pwm1
2) Change INTERVAL
3) Just quit
4) Save and quit
5) Show configuration
select (1-n): 1

Devices:
hwmon0 is acpitz
hwmon1 is BAT0
hwmon2 is nvme
hwmon3 is amdgpu
hwmon4 is AC
hwmon5 is k10temp
hwmon6 is thinkpad
hwmon7 is ath11k_hwmon

Current temperature readings are as follows:
hwmon0/temp1_input  20
hwmon2/temp1_input  38
hwmon2/temp2_input  38
hwmon2/temp3_input  38
hwmon3/temp1_input  32
hwmon5/temp1_input  32
hwmon6/temp1_input  32
cat: hwmon6/temp2_input: No such device or address
/usr/sbin/pwmconfig: line 908: let: S= / 1000: syntax error: operand expected 
(error token is "/ 1000")
hwmon6/temp2_input  
hwmon6/temp3_input  32
hwmon6/temp4_input  0
hwmon6/temp5_input  32
hwmon6/temp6_input  32
hwmon6/temp7_input  32
cat: hwmon6/temp8_input: No such device or address
/usr/sbin/pwmconfig: line 908: let: S= / 1000: syntax error: operand expected 

Bug#1029148: pwmconfig: DELAY=5 too low on a Lenovo Thinkpad T14s Gen3 AMD -> "no correlation"

[Linus Lüssing]

Package: fancontrol
Version: 1:3.6.0-7.1
Severity: normal
X-Debbugs-Cc: linus.luess...@c0d3.blue

Dear Maintainer,

The DELAY=5 seems to be too low for a Lenovo Thinkpad T14s Gen3 AMD. I'm
getting the "no correlation" message when pwmconfig tries to detect the
PWM->fan correlation.

Once I see the message "Testing pwm control hwmon6/pwm1 ..." I do
immediately hear the fan to go from its disengaged maximum of 4900 RPM
to 0 nearly instantly, however it seems it takes a while to get propagated
to /sys/class/hwmon/hwmon6/fan1_input.

In my tests DELAY=10 seems to be at the border, it usually works but
sometimes fails. DELAY=12 or greater seems to be reliable.

You can find a few example outputs (with some extra debug output lines
I had added) for various DELAY values below.

The UEFI System Firmware should be the latest available today (0.1.25
according to fwupdmgr).

Regards, Linus


*** 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: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 6.1.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 fancontrol depends on:
ii  init-system-helpers1.65.2
ii  sysvinit-utils [lsb-base]  3.06-2

fancontrol recommends no packages.

fancontrol suggests no packages.

-- no debconf information



DELAY=5:

$ sudo pwmconfig
# pwmconfig version 3.6.0
This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.

We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.

Found the following devices:
   hwmon0 is acpitz
   hwmon1 is BAT0
   hwmon2 is nvme
   hwmon3 is amdgpu
   hwmon4 is AC
   hwmon5 is k10temp
   hwmon6 is thinkpad
   hwmon7 is ath11k_hwmon

Found the following PWM controls:
   hwmon6/pwm1   current value: 0

Giving the fans some time to reach full speed...
Found the following fan sensors:
   hwmon6/fan1_input current speed: 4926 RPM

Warning!!! This program will stop your fans, one at a time,
for approximately 5 seconds each!!!
This may cause your processor temperature to rise!!!
If you do not want to do this hit control-C now!!!
Hit return to continue: 

Testing pwm control hwmon6/pwm1 ...
~~~ i: hwmon6/pwm1, calling: pwmset hwmon6/pwm1 0 (fan1_input: 65535, pwm1: 255)
~~~ i: hwmon6/pwm1, after calling: pwmset hwmon6/pwm1 0 (fan1_input: 65535, 0)
~~~ i: hwmon6/pwm1, after calling: pwmset hwmon6/pwm1 0; sleep 5 (fan1_input: 
4934, 0)
~~~ CURRENT_SPEED: 4934, SPEEDS: 4926
~~~ j in GOODFAN: hwmon6/fan1_input in hwmon6/fan1_input
  hwmon6/fan1_input ... speed was 4926 now 4934
~~~ S: 4934, threshold: 3694, OS: 4926
no correlation

No correlations were detected.
There is either no fan connected to the output of hwmon6/pwm1,
or the connected fan has no rpm-signal connected to one of
the tested fan sensors. (Note: not all motherboards have
the pwm outputs connected to the fan connectors,
check out the hardware database on http://www.almico.com/forumindex.php)

Did you see/hear a fan stopping during the above test (n)? 



DELAY=7:

$ sudo pwmconfig
# pwmconfig version 3.6.0
This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.

We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.

Found the following devices:
   hwmon0 is acpitz
   hwmon1 is BAT0
   hwmon2 is nvme
   hwmon3 is amdgpu
   hwmon4 is AC
   hwmon5 is k10temp
   hwmon6 is thinkpad
   hwmon7 is ath11k_hwmon

Found the following PWM controls:
   hwmon6/pwm1   current value: 0

Giving the fans some time to reach full speed...
Found the following fan sensors:
   hwmon6/fan1_input current speed: 4926 RPM

Warning!!! This program will stop your fans, one at a time,
for 

Bug#1028549: Acknowledgement (xserver-xorg-video-radeon: [Radeon 680M]: not rendering/refreshing fullscreen properly with VSync off)

[Linus Lüssing]

PS: Device with the integrated ATI/AMD Rembrandt Radeon 680M
via the AMD Ryzen 7 PRO 6850U I'm having this issue with:
A Thinkpad T14s Gen3 AMD laptop.

Bug#1028549: xserver-xorg-video-radeon: [Radeon 680M]: not rendering/refreshing fullscreen properly with VSync off

[Linus Lüssing]

Package: xserver-xorg-video-radeon
Version: 1:19.1.0-3
Severity: normal
X-Debbugs-Cc: linus.luess...@c0d3.blue

Dear Maintainer,

When I start for instance Neverball on Xmonad and either:

* set it to fullscreen with, vsync=off or
* set it to windowed but resize it / show it fullscreen via the Xmonad
  fullscreen layout

Then I get the following issue:

* The start screen with its 3D animated background is only
  rendering/refreshing if I move the mouse pointer and then only the
  few vertical lines around this mouse pointer. I can switch to
  another TTY and back to the Xmonad TTY, but if I do this a few
  times then the system hangs completely.

If I either enable VSync for Neverball or if Neverball is not occupying
the full screen then I don't get any rendering issues.

I could reproduce the issue with the following window managers which
I selected from the LightDM login greeter:

* Xmonad, i3, dwm, Gnome (with X11), Mate with "xmonad --replace"

I could not reproduce the issue with the following window managers:

* Gnome (Wayland) or Mate (as is, without "xmonad --replace")

Applications I could reproduce it with:

* Neverball, Warzone2100 (with all 3 gfxbackend options:
  opengl, opengles, vulkan), 0ad


Tested on latest Debian Sid, Linux 6.1.4-1. Firmwares should be up to date,
updated EFI/system firmwares via fwupdmgr and installed the latest
firmware-amd-graphics package from non-free (20221214-3). There is no
later Yellow-dog firmware for firmware-amd-graphics in its Git
repository.

I'm hoping this is the right Debian package to report this to (or should
this better be the firmware-amd-graphics package?).

Cheers, Linus


*** 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 ***


-- Package-specific info:
/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.

VGA-compatible devices on PCI bus:
--
33:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Rembrandt [Radeon 680M] [1002:1681] (rev d1)

/etc/X11/xorg.conf does not exist.

Contents of /etc/X11/xorg.conf.d:
-
total 0

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/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)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 41759 Jan 12 13:25 /var/log/Xorg.1.log
-rw-r--r-- 1 root root 40850 Jan 12 16:18 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[   747.649] 
X.Org X Server 1.21.1.6
X Protocol Version 11, Revision 0
[   747.649] Current Operating System: Linux linus-lptp 6.1.0-1-amd64 #1 SMP 
PREEMPT_DYNAMIC Debian 6.1.4-1 (2023-01-07) x86_64
[   747.649] Kernel command line: BOOT_IMAGE=/vmlinuz-6.1.0-1-amd64 
root=/dev/mapper/main--vg-root ro quiet
[   747.649] xorg-server 2:21.1.6-1 (https://www.debian.org/support) 
[   747.649] Current version of pixman: 0.42.2
[   747.649]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   747.649] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   747.649] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jan 12 16:18:48 
2023
[   747.649] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   747.649] (==) No Layout section.  Using the first Screen section.
[   747.649] (==) No screen section available. Using defaults.
[   747.649] (**) |-->Screen "Default Screen Section" (0)
[   747.649] (**) |   |-->Monitor ""
[   747.649] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[   747.649] (==) Automatically adding devices
[   747.649] (==) Automatically enabling devices
[   747.649] (==) Automatically adding GPU devices
[   747.649] (==) Automatically binding GPU devices
[   747.649] (==) Max clients allowed: 256, resource mask: 0x1f
[   747.649] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   747.649]Entry deleted from font path.
[   747.649] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[   747.649]Entry deleted from font path.
[   747.649] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[   747.649]Entry deleted from font path.

Bug#1027981: grub-efi-amd64-bin: add grub2 master to experimental? cryptomount detached header feature

[Linus Lüssing]

Package: grub-efi-amd64-bin
Version: 2.06-7
Severity: wishlist
X-Debbugs-Cc: linus.luess...@c0d3.blue

Dear Maintainer,

I would like to try the new LUKS detached header feature that was added
to GRUB2 in the master branch to the cryptomount command. It is not part
of a release yet though.

Would it be possible to add Debian packages of GRUB2's master branch to
Debian experimental? Or alternatively, has anyone prepared something
similar somewhere else already?

I started to try to use the "debian" folder from
"apt-get source grub-efi-amd64-bin" on Debian Sid within a GRUB2 git
repository checkout and then using "debuild -us -uc". However some
patches don't apply cleanly anymore.

Regards, Linus

Bug#997006: closed by Debian FTP Masters (reply to Michael Biebl ) (Bug#997006: fixed in systemd 247.3-7)

[Linus Lüssing]

Just tried 247.3-7 and it fixes the LXD systemd-networkd issue for
me. Thanks a lot for your great maintenance work, will forward the
good news to the LXD forum once it propagates from
stable-proposed-updates to stable. I'm sure a lot of people there
will be happy about this, too.

Regards, Linus


On Mon, Mar 21, 2022 at 12:48:19PM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the systemd package:
> 
> #997006: systemd-networkd: broken/regression in unprivileged LXD container in 
> v247
> 
> It has been closed by Debian FTP Masters  
> (reply to Michael Biebl ).
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Debian FTP Masters 
>  (reply to Michael Biebl ) 
> by
> replying to this email.
> 
> 
> -- 
> 997006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997006
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

> Date: Mon, 21 Mar 2022 12:47:07 +
> From: Debian FTP Masters 
> To: 997006-cl...@bugs.debian.org
> Subject: Bug#997006: fixed in systemd 247.3-7
> 

> Date: Fri, 22 Oct 2021 11:43:47 +0200
> From: Linus Lüssing 
> To: Debian Bug Tracking System 
> Subject: systemd-networkd: broken/regression in unprivileged LXD container
>  in v247
> 
> Package: systemd
> Version: 247.3-6
> Severity: normal
> Tags: upstream
> X-Debbugs-Cc: linus.luess...@c0d3.blue
> 
> Hi,
> 
> We found that using systemd-networkd in an unprivileged LXD container is
> broken in systemd v247. A network or link file is not attached to an
> interface and instead "networkctl -l status eth0" shows "n/a" for the
> "Link File" and "Network File". Leading to the network interface not being
> configured at all. systemd v246 and v248/v249 work fine, so it is a
> regression specific to v247.
> 
> Bisect'ing shows that this commit introduced the bug for v247:
> 
> https://github.com/systemd/systemd/commit/88da55e28b467999da005591d3252a98f4436522
> 
> And the following commit fixed it again for v248:
> 
> https://github.com/systemd/systemd/commit/0e789e6d48046d43c50dd949a71ac56f1127bb96
> 
> Git cherry-picking 0e789e6d4 onto v247 fixes the issue (cherry-picking does
> not apply cleanly but resolving this is straight forward).
> 
> Furthermore systemd-networkd does not work if the udev package is
> missing (same symptoms, no link or network file gets attached to the
> interface).
> 
> 
> Suggestions to fix:
> 
> * Add a dependency to the systemd package for the udev package.
> * Backport 0e789e6d4 to the systemd v247 package.
> 
> Alternatively (or additionally) systemd v249 could be added to
> bullseye-backports, so people using Debian Bullseye could work around
> the issue by installing systemd v249.
> 
> For more details see the following links:
> 
> https://discuss.linuxcontainers.org/t/systemd-networkd-not-working-in-debian-sid-or-bullseye-images/11503/17
> https://github.com/systemd/systemd/pull/18559
> 
> Regards, Linus
> 
> 
> 
> -- Package-specific info:
> 
> -- System Information:
> Debian Release: 11.1
>   APT prefers stable-security
>   APT policy: (500, 'stable-security'), (500, 'stable')
> Architecture: arm64 (aarch64)
> 
> Kernel: Linux 5.9.2-v8+ (SMP w/4 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_CRAP
> Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages systemd depends on:
> ii  adduser  3.118
> ii  libacl1  2.2.53-10
> ii  libapparmor1 2.13.6-10
> ii  libaudit11:3.0-2
> ii  libblkid12.36.1-8
> ii  libc62.31-13+deb11u2
> ii  libcap2  1:2.44-1
> ii  libcrypt11:4.4.18-4
> ii  libcryptsetup12  2:2.3.5-1
> ii  libgcrypt20  1.8.7-6
> ii  libgnutls30  3.7.1-5
> ii  libgpg-error01.38-2
> ii  libip4tc21.8.7-1
> ii  libkmod2 28-1
> ii  liblz4-1 1.9.3-2
> ii  liblzma5 5.2.5-2
> ii  libmount12.36.1-8
> ii  libpam0g 1.4.0-9+deb11u1
> ii  libseccomp2  2.5.1-1
> ii  libselinux1  3.1-3
> ii  libsystemd0 

Bug#997006: systemd-networkd: broken/regression in unprivileged LXD container in v247

[Linus Lüssing]

Package: systemd
Version: 247.3-6
Severity: normal
Tags: upstream
X-Debbugs-Cc: linus.luess...@c0d3.blue

Hi,

We found that using systemd-networkd in an unprivileged LXD container is
broken in systemd v247. A network or link file is not attached to an
interface and instead "networkctl -l status eth0" shows "n/a" for the
"Link File" and "Network File". Leading to the network interface not being
configured at all. systemd v246 and v248/v249 work fine, so it is a
regression specific to v247.

Bisect'ing shows that this commit introduced the bug for v247:

https://github.com/systemd/systemd/commit/88da55e28b467999da005591d3252a98f4436522

And the following commit fixed it again for v248:

https://github.com/systemd/systemd/commit/0e789e6d48046d43c50dd949a71ac56f1127bb96

Git cherry-picking 0e789e6d4 onto v247 fixes the issue (cherry-picking does
not apply cleanly but resolving this is straight forward).

Furthermore systemd-networkd does not work if the udev package is
missing (same symptoms, no link or network file gets attached to the
interface).


Suggestions to fix:

* Add a dependency to the systemd package for the udev package.
* Backport 0e789e6d4 to the systemd v247 package.

Alternatively (or additionally) systemd v249 could be added to
bullseye-backports, so people using Debian Bullseye could work around
the issue by installing systemd v249.

For more details see the following links:

https://discuss.linuxcontainers.org/t/systemd-networkd-not-working-in-debian-sid-or-bullseye-images/11503/17
https://github.com/systemd/systemd/pull/18559

Regards, Linus



-- Package-specific info:

-- System Information:
Debian Release: 11.1
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)

Kernel: Linux 5.9.2-v8+ (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  adduser  3.118
ii  libacl1  2.2.53-10
ii  libapparmor1 2.13.6-10
ii  libaudit11:3.0-2
ii  libblkid12.36.1-8
ii  libc62.31-13+deb11u2
ii  libcap2  1:2.44-1
ii  libcrypt11:4.4.18-4
ii  libcryptsetup12  2:2.3.5-1
ii  libgcrypt20  1.8.7-6
ii  libgnutls30  3.7.1-5
ii  libgpg-error01.38-2
ii  libip4tc21.8.7-1
ii  libkmod2 28-1
ii  liblz4-1 1.9.3-2
ii  liblzma5 5.2.5-2
ii  libmount12.36.1-8
ii  libpam0g 1.4.0-9+deb11u1
ii  libseccomp2  2.5.1-1
ii  libselinux1  3.1-3
ii  libsystemd0  247.3-6
ii  libzstd1 1.4.8+dfsg-2.1
ii  mount2.36.1-8
ii  systemd-timesyncd [time-daemon]  247.3-6
ii  util-linux   2.36.1-8

Versions of packages systemd recommends:
ii  dbus  1.12.20-2

Versions of packages systemd suggests:
pn  policykit-1
pn  systemd-container  

Versions of packages systemd is related to:
pn  dracut   
pn  initramfs-tools  
ii  libnss-systemd   247.3-6
ii  libpam-systemd   247.3-6
pn  udev 

-- Configuration Files:
/etc/systemd/journald.conf changed:
[Journal]

/etc/systemd/logind.conf changed:
[Login]

/etc/systemd/resolved.conf changed:
[Resolve]


-- no debconf information

Bug#996930: warzone2100: Can't play multiplayer through lobby: "Can't find any games for your version"

[Linus Lüssing]

Package: warzone2100
Version: 3.3.0-4+b1
Severity: normal

Hi,

When trying to play a multiplayer game through the lobby, the following
error is returned:

"Can't find any game for your version. -
Download 4.1.3 - 3.1.5 & 3.2.3 are unsupported!"

To avoid breaking lobby multiplayer it would be great if at least Sid
could always follow and provide the latest release.

Skirmish and multiplayer work fine for me when building and running
Warzone2100 4.1.3 from the source.

I haven't tried campaign for a while but several release notes mention
campaign fixes, too. So might help with #862917 as well.

Regards, Linus


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

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

Versions of packages warzone2100 depends on:
ii  libc6 2.32-2
ii  libfreetype6  2.10.4+dfsg-1
ii  libgcc-s1 10.2.1-6
ii  libgl11.3.2-1
ii  libglew2.22.2.0-4
ii  libharfbuzz0b 2.7.4-1
ii  libminiupnpc172.1-1+b2
ii  libogg0   1.3.2-1+b1
ii  libopenal11:1.19.1-2
ii  libphysfs13.0.2-5
ii  libpng16-16   1.6.37-3
ii  libqt5core5a  5.15.2+dfsg-5
ii  libqt5gui55.15.2+dfsg-5
ii  libqt5script5 5.15.2+dfsg-2
ii  libqt5widgets55.15.2+dfsg-5
ii  libsdl2-2.0-0 2.0.14+dfsg2-3
ii  libstdc++610.2.1-6
ii  libtheora01.1.1+dfsg.1-15
ii  libvorbis0a   1.3.7-1
ii  libvorbisfile31.3.7-1
ii  warzone2100-data  3.3.0-4
ii  zlib1g1:1.2.11.dfsg-2

Versions of packages warzone2100 recommends:
ii  warzone2100-music  3.3.0-4

warzone2100 suggests no packages.

-- no debconf information

Bug#873443: closed by Rene Engelhard <r...@debian.org> (Bug#873443: fixed in libreoffice 1:5.4.1-1)

[Linus Lüssing]

On Thu, Aug 31, 2017 at 11:39:17AM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the libreoffice-core package:
> 
> #873443: terminate called after throwing an instance of 
> com::sun::star::uno::DeploymentException on architectures not using 
> libmergedlo.so
> 
> It has been closed by Rene Engelhard .

Hi Rene,

The buildbot finally finished for armhf and it works like charm
\o/.

And, wow, quite a changelog, thanks for the great work, Rene :-).

Cheers, Linus

Bug#873443: uno-libs3: Fatal exception: Signal 6

[Linus Lüssing]

Hi Rene,

Thanks for the quick reply!

On Sun, Aug 27, 2017 at 10:54:10PM +0200, Rene Engelhard wrote:
> On Sun, Aug 27, 2017 at 09:16:25PM +0200, linus.luess...@c0d3.blue wrote:
> > The device I'm using is armhf/armv7 based: An Odroid U3 featuring
> > a Samsung Exynos 4412 ARM processor which includes a Mali-400 MP VG/3D
> > GPU.
> 
> ... which needs non-free, binary only drivers, ttbomk?


I'm running the Odroid U3 with a clean, free Debian Sid repo and a
vanilla 4.2.3 Linux kernel. Root partition was installed via
debootstrap from Debian Sid / free-only. And the kernel was
self-compiled from the vanilla, unmodified Linux kernel git. I'm
neither using the hackish kernel provided by the vendor, Hardkernel,
nor did I install any non-free Debian packages, firmwares or kernel
modules. The upstream support with free software is actually pretty
nice for this device :-). Even Device Tree Sources are available in
the vanilla kernel for the U3.

As far as I understood, the only proprietary software used is
some signed, small, proprietary binary blob in the first bytes
of the flash memory / eMMC card. To initialize graphics
first which then loads the bootloader (u-boot) which then loads
the kernel (as far as I understood).

> [...]
> > Is there a way to deactivate OpenGL in some config file
> > for libreoffice?
> 
> https://wiki.documentfoundation.org/OpenGL
> 
> I thought there was some envvar, too, but don't find it right now...
> 
> I *think* "safe mode" (libreoffice –safe-mode) also disables OpenGL...

"$ libreoffice --safe-mode" did not help, same crash.

I noticed, that running "$ libreoffice -h" crashed, too. However,
that one only fails with the very first line ("terminate called
after..."). The "Fatal exception" and stack trace is missing
on the command line output then.

Regards, Linus

Bug#867733: closed by Dmitry Shachnev <mity...@debian.org> (Bug#867733: fixed in pyqt5 5.7+dfsg-6)

[Linus Lüssing]

On Wed, Aug 23, 2017 at 01:37:44PM +0300, Dmitry Shachnev wrote:
> This armhf build bot is currently building Qt WebEngine itself.
> If it succeeds then pyqt5 should be also built soon.
> 
> The mipsel build of python3-pyqt5.qtwebengine is now available.
> 

Thanks a lot, Dmitry - installs just fine now! :-)

Regards, Linus

Bug#867733: closed by Dmitry Shachnev <mity...@debian.org> (Bug#867733: fixed in pyqt5 5.7+dfsg-6)

[Linus Lüssing]

Hi Dmitry,

Thanks for looking at this issue, both in experimental and
unstable.

The changelog mentions arm64, armhf and mipsel. However I
only see amd64, arm64 and i386 in experimental/unstable for
python3-pyqt5.qtwebengine on packages.debian.org [0][1].

Were armhf and mispel accidentally forgotten? Or did some build
bots choke on those?

Regards, Linus

[0]: https://packages.debian.org/sid/python3-pyqt5.qtwebengine
[1]: https://packages.debian.org/experimental/python3-pyqt5.qtwebengine


On Tue, Aug 22, 2017 at 12:09:03PM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the python3-pyqt5.qtwebengine package:
> 
> #867733: mnemosyne: Package not installable on armhf, dependency issues
> 
> It has been closed by Dmitry Shachnev .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Dmitry Shachnev 
>  by
> replying to this email.
> 
> 
> -- 
> 867733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867733
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

> Date: Tue, 22 Aug 2017 12:06:12 +
> From: Dmitry Shachnev 
> To: 867733-cl...@bugs.debian.org
> Subject: Bug#867733: fixed in pyqt5 5.7+dfsg-6
> 
> Source: pyqt5
> Source-Version: 5.7+dfsg-6
> 
> We believe that the bug you reported is fixed in the latest version of
> pyqt5, which is due to be installed in the Debian FTP archive.
> 
> A summary of the changes between this version and the previous one is
> attached.
> 
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 867...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
> 
> Debian distribution maintenance software
> pp.
> Dmitry Shachnev  (supplier of updated pyqt5 package)
> 
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
> 
> 
> Format: 1.8
> Date: Tue, 22 Aug 2017 14:41:04 +0300
> Source: pyqt5
> Binary: pyqt5-dev pyqt5-dev-tools pyqt5-doc pyqt5-examples python3-pyqt5 
> python3-pyqt5-dbg python3-dbus.mainloop.pyqt5 python3-dbus.mainloop.pyqt5-dbg 
> python3-pyqt5.qtopengl python3-pyqt5.qtopengl-dbg python3-pyqt5.qtsql 
> python3-pyqt5.qtsql-dbg python3-pyqt5.qtwebchannel 
> python3-pyqt5.qtwebchannel-dbg python3-pyqt5.qtwebengine 
> python3-pyqt5.qtwebengine-dbg python3-pyqt5.qtwebkit 
> python3-pyqt5.qtwebkit-dbg python3-pyqt5.qtwebsockets 
> python3-pyqt5.qtwebsockets-dbg python3-pyqt5.qtxmlpatterns 
> python3-pyqt5.qtxmlpatterns-dbg python3-pyqt5.qtsvg python3-pyqt5.qtsvg-dbg 
> python3-pyqt5.qtmultimedia python3-pyqt5.qtmultimedia-dbg 
> python3-pyqt5.qtquick python3-pyqt5.qtquick-dbg python3-pyqt5.qtserialport 
> python3-pyqt5.qtserialport-dbg python3-pyqt5.qtsensors 
> python3-pyqt5.qtsensors-dbg python3-pyqt5.qtx11extras 
> python3-pyqt5.qtx11extras-dbg python3-pyqt5.qtpositioning 
> python3-pyqt5.qtpositioning-dbg python-pyqt5 python-pyqt5-dbg 
> python-dbus.mainloop.pyqt5
>  python-dbus.mainloop.pyqt5-dbg python-pyqt5.qtopengl 
> python-pyqt5.qtopengl-dbg python-pyqt5.qtsql python-pyqt5.qtsql-dbg 
> python-pyqt5.qtwebchannel python-pyqt5.qtwebchannel-dbg 
> python-pyqt5.qtwebengine python-pyqt5.qtwebengine-dbg python-pyqt5.qtwebkit 
> python-pyqt5.qtwebkit-dbg python-pyqt5.qtwebsockets 
> python-pyqt5.qtwebsockets-dbg python-pyqt5.qtxmlpatterns 
> python-pyqt5.qtxmlpatterns-dbg python-pyqt5.qtsvg python-pyqt5.qtsvg-dbg 
> python-pyqt5.qtmultimedia python-pyqt5.qtmultimedia-dbg python-pyqt5.qtquick 
> python-pyqt5.qtquick-dbg python-pyqt5.qtserialport 
> python-pyqt5.qtserialport-dbg python-pyqt5.qtsensors 
> python-pyqt5.qtsensors-dbg python-pyqt5.qtx11extras 
> python-pyqt5.qtx11extras-dbg python-pyqt5.qtpositioning
>  python-pyqt5.qtpositioning-dbg
> Architecture: source
> Version: 5.7+dfsg-6
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian Python Modules Team 
> 
> Changed-By: Dmitry Shachnev 
> Description:
>  pyqt5-dev  - Development files for PyQt5
>  pyqt5-dev-tools - Development tools for PyQt5
>  pyqt5-doc  - Documentation for PyQt5
>  pyqt5-examples - Examples and demos for PyQt5
>  python-dbus.mainloop.pyqt5 - D-Bus Qt main loop support for Python 2
>  python-dbus.mainloop.pyqt5-dbg - D-Bus Qt main loop support for Python 2 
> (debug extension)
>  python-pyqt5 - Python 2 bindings for Qt5
>  python-pyqt5-dbg - Python 2 bindings for Qt5 (debug extensions)
>  python-pyqt5.qtmultimedia - Python 2 bindings for Qt5's Multimedia module
>  python-pyqt5.qtmultimedia-dbg - Python 2 bindings for Qt5's Multimedia 
> module (debug 

Bug#856487: pulseaudio: SIGSEGV upon streaming to bluetooth headset

[Linus Lüssing]

On Sat, Mar 04, 2017 at 07:37:36PM -0300, Felipe Sateler wrote:
> > Not really familiar with how binaries get created or uploaded in
> > Debian, but is it possible to determine the gcc + binutils
> > versions with which libsbc 1.3-1 and 1.3-1+b2 were created? Just
> > to double check whether the official uploads were indeed created
> > with gcc-4.9 for libsbc 1.3-1 and gcc-5/gcc-6 for 1.3-1+b2?
> 
> The build logs are publicly available, for this build[1] the versions used 
> were:
> 
> binutils_2.25-8
> gcc-4.9_4.9.2-19
> 
> [1] 
> https://buildd.debian.org/status/fetch.php?pkg=sbc=armhf=1.3-1=1433137735=0

Aiy, ok, thanks a lot, Felipe!

Is there anything else I could do? Was the issue reported to the
gcc folks somewhere yet or should I report it to some bugtracker of
the gcc project?

Bug#856487: pulseaudio: SIGSEGV upon streaming to bluetooth headset

[Linus Lüssing]

> Are you sure it's definitely related to the gcc version? Did you actually
> try rebuilding with gcc-4.9 on the target machine?
>
> The thing is that assembly code is not interpreted by gcc but by the assembler
> which is part of the binutils package. Since binutils is updated
> in Debian very often, it may be well related to a bug in binutils.

I didn't try from a chroot, but tried 2.28 as you suggested as
well as a few downgraded versions, which all failed:

binutils 2.28-1 -> not 
binutils 2.27.51.20161220-1
binutils 2.27-9 -> not working
binutils 2.26-1 -> not working
binutils 2.26.1-1 -> not working
binutils 2.26-12 -> not working

I also tried downgrading gcc-6, which didn't help either:
gcc 6.0.1-2

What worked then:
* gcc 4.9.4-2 + binutils 2.26.1-1
* gcc 4.9.4-2 + binutils 2.28-1


Not really familiar with how binaries get created or uploaded in
Debian, but is it possible to determine the gcc + binutils
versions with which libsbc 1.3-1 and 1.3-1+b2 were created? Just
to double check whether the official uploads were indeed created
with gcc-4.9 for libsbc 1.3-1 and gcc-5/gcc-6 for 1.3-1+b2?

Regards, Linus

PS: All those tests above just with a plain
"$ CC=gcc-{4.9,6} dpkg-buildpackage -us -uc", so with the default
hardening flags.

Bug#856487: pulseaudio: SIGSEGV upon streaming to bluetooth headset

[Linus Lüssing]

On Fri, Mar 03, 2017 at 01:14:56PM -0300, Felipe Sateler wrote:
> It has been pointed out to me that this may be unrelated to PIE, but
> just caused by a newer GCC version. Could you check if disabling PIE
> makes the binary work again? To do so:
> 
> apt-get source sbc
> sudo apt-get build-dep sbc
> cd sbc-1.3
> DEB_BUILD_OPTIONS=hardening=-pie dpkg-buildpackage -us -uc
> sudo dpkg -i ../libsbc1_*.deb

Tried it, but still crashes. I also tried:

0) dpkg-buildpackage -us -uc
1) 
DEB_BUILD_OPTIONS=hardening=-stackprotectorstrong,-stackprotector,-pie,-fortify 
dpkg-buildpackage -us -uc
2) DEB_BUILD_OPTIONS=hardening=-all dpkg-buildpackage -us -uc
3) CC=gcc-5 dpkg-buildpackage -us -uc

But the resulting packages/libraries crash, too.

~~~
$ gcc --version
gcc (Debian 6.3.0-8) 6.3.0 20170221
$ gcc-5 --version
gcc-5 (Debian 5.4.1-5) 5.4.1 20170205
~~~

What seems to work though:
~~~
$ CC=clang dpkg-buildpackage -us -uc
[...]
$ sudo dpkg -i ../libsbc1_*.deb
~~~

Regards, Linus

Bug#856487: pulseaudio: SIGSEGV upon streaming to bluetooth headset

[Linus Lüssing]

On Thu, Mar 02, 2017 at 08:36:29PM -0300, Felipe Sateler wrote:
> Indeed. However, from what I can see the most likely (only?) way to
> get there is via a sbc_encode that is called in module-bluez5-device.
> However, that part of the code does not look changed since 9.0. Have
> you confirmed downgrading to 9.0 fixes the issue?

Oh, sorry, good point. I think we are narrowing it down now:

It's actually not the pulsaudio upgrade from 9.0 to 10 but the
update of libsbc1 from 1.3-1 to 1.3-1+b2, which I did during the
same "apt-get dist-upgrade".

Downgrading libsbc1 to 1.3-1 is enough to make the crash vanish!

Regards, Linus

Bug#856487: pulseaudio: SIGSEGV upon streaming to bluetooth headset

[Linus Lüssing]

On Thu, Mar 02, 2017 at 06:29:12PM -0300, Felipe Sateler wrote:
> Could you install the debug symbols for libsbc and see if we can get a
> reasonable function name for that call?

Now with sbc-dbg installed:
https://metameute.de/~tux/bugreport/pulseaudio/core.pulseaudio.1001.d834b6de713f4e04816eb5b83e7100a3.3259.1488493325.lz4
https://metameute.de/~tux/bugreport/pulseaudio/pulseaudio-3.log
https://metameute.de/~tux/bugreport/pulseaudio/pulseaudio-3.core.xz


And here is the gdb backtrace for all threads again, now with a
little more information :) :

#
odroid@otheros:/$ sudo coredumpctl gdb
   PID: 3259 (pulseaudio)
   UID: 1001 (odroid)
   GID: 1001 (odroid)
Signal: 11 (SEGV)
 Timestamp: Thu 2017-03-02 23:22:05 CET (2min 51s ago)
  Command Line: pulseaudio -
Executable: /usr/bin/pulseaudio
 Control Group: /system.slice/tigervncserver.service
  Unit: tigervncserver.service
 Slice: system.slice
   Boot ID: d834b6de713f4e04816eb5b83e7100a3
Machine ID: 5716166b59b3477b83939474094b846e
  Hostname: otheros
   Storage: 
/var/lib/systemd/coredump/core.pulseaudio.1001.d834b6de713f4e04816eb5b83e7100a3.3259.1488493325.lz4
   Message: Process 3259 (pulseaudio) of user 1001 dumped core.

Stack trace of thread 3283:
#0  0xa0c84962 sbc_analyze_eight_armv6 (libsbc.so.1)
#1  0x000c0018 n/a (n/a)

GNU gdb (Debian 7.12-6) 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 "arm-linux-gnueabihf".
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/pulseaudio...Reading symbols from 
/usr/lib/debug/.build-id/1b/d03b66bbc1da7b639af9914dd3db452a0905f2.debug...done.
done.
[New LWP 3283]
[New LWP 3259]
[New LWP 3263]
[New LWP 3262]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Core was generated by `pulseaudio -'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0xa0c84962 in sbc_analyze_eight_armv6 () at sbc/sbc_primitives_armv6.c:115
115 sbc/sbc_primitives_armv6.c: Datei oder Verzeichnis nicht gefunden.
[Current thread is 1 (Thread 0xa0c79300 (LWP 3283))]
(gdb) thread apply all bt

Thread 4 (Thread 0xb204b300 (LWP 3262)):
#0  __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:46
#1  0xb6be4506 in __GI_ppoll (fds=0x7f6b6ad0, nfds=3, timeout=, 
timeout@entry=0x0, sigmask=sigmask@entry=0x0) at 
../sysdeps/unix/sysv/linux/ppoll.c:39
#2  0xb6e47846 in ppoll (__ss=0x0, __timeout=0x0, __nfds=, 
__fds=) at /usr/include/arm-linux-gnueabihf/bits/poll2.h:77
#3  pa_rtpoll_run (p=0x7f5f8388) at pulsecore/rtpoll.c:314
#4  0xb206a3c8 in thread_func (userdata=0x7f695c58) at 
modules/alsa/alsa-sink.c:1799
#5  0xb6df8970 in internal_thread_func (userdata=0x7f62a738) at 
pulsecore/thread-posix.c:81
#6  0xb6cea5e4 in start_thread (arg=0x0) at pthread_create.c:335
#7  0xb6bea472 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:86 from 
/lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 3 (Thread 0xb16ff300 (LWP 3263)):
#0  __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:46
#1  0xb6be4506 in __GI_ppoll (fds=0x7f62a5d0, nfds=2, timeout=, 
timeout@entry=0x0, sigmask=sigmask@entry=0x0) at 
../sysdeps/unix/sysv/linux/ppoll.c:39
#2  0xb6e47846 in ppoll (__ss=0x0, __timeout=0x0, __nfds=, 
__fds=) at /usr/include/arm-linux-gnueabihf/bits/poll2.h:77
#3  pa_rtpoll_run (p=0x7f5f04d8) at pulsecore/rtpoll.c:314
#4  0xb206f2fe in thread_func (userdata=0x7f60aec0) at 
modules/alsa/alsa-source.c:1516
#5  0xb6df8970 in internal_thread_func (userdata=0x7f6246d0) at 
pulsecore/thread-posix.c:81
#6  0xb6cea5e4 in start_thread (arg=0x0) at pthread_create.c:335
#7  0xb6bea472 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:86 from 
/lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 2 (Thread 0xb6f39000 (LWP 3259)):
#0  0xb6cf1420 in write () at ../sysdeps/unix/syscall-template.S:84
#1  0xb6dd611e in pa_write (fd=43, buf=buf@entry=0xbebff1e8, 
count=count@entry=8, type=type@entry=0x7f66c13c) at pulsecore/core-util.c:477
#2  0xb6ddb0a8 in pa_fdsem_post (f=0x7f66c130) at pulsecore/fdsem.c:196
#3  

Bug#856487: pulseaudio: SIGSEGV upon streaming to bluetooth headset

[Linus Lüssing]

On Thu, Mar 02, 2017 at 03:27:25AM +0100, Linus Lüssing wrote:
> Two more notes to maybe eliminate some potential causes:
> 
> * Removing the ~/.config/pulse/default.pa mentioned earlier did not help.
> * Using a different bluetooth stick did not help (Some Logilink
>   one now which worked with pulseaudio v9, too, listed as:
>   "0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)" )

And two more tests:

* Using another bluetooth headset crashes, too (Medion 43316).
* Selecting HSP/HFP instead of A2DP in pavucontrol makes playback
  work! The crash only happens when A2DP is selected.

Bug#856487: pulseaudio: SIGSEGV upon streaming to bluetooth headset

[Linus Lüssing]

Two more notes to maybe eliminate some potential causes:

* Removing the ~/.config/pulse/default.pa mentioned earlier did not help.
* Using a different bluetooth stick did not help (Some Logilink
  one now which worked with pulseaudio v9, too, listed as:
  "0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)" )

Bug#856487: pulseaudio: SIGSEGV upon streaming to bluetooth headset

[Linus Lüssing]

On Wed, Mar 01, 2017 at 07:34:11PM -0300, Felipe Sateler wrote:
> You need to activate the debug archives:
> 
> https://wiki.debian.org/AutomaticDebugPackages

Aiy, thanks! The following crash was with pulseaudio-dbgsym and
libpulse0-dbgsym installed and the gdb backtrace was created for
all threads ("(gdb) thread apply all bt" - unfortunately still looks
like there is some stack corruption :( ) :

#
odroid@otheros:/$ sudo coredumpctl gdb
   PID: 11356 (pulseaudio)
   UID: 1001 (odroid)
   GID: 1001 (odroid)
Signal: 11 (SEGV)
 Timestamp: Thu 2017-03-02 02:24:15 CET (8min ago)
  Command Line: pulseaudio -
Executable: /usr/bin/pulseaudio
 Control Group: /system.slice/tigervncserver.service
  Unit: tigervncserver.service
 Slice: system.slice
   Boot ID: d834b6de713f4e04816eb5b83e7100a3
Machine ID: 5716166b59b3477b83939474094b846e
  Hostname: otheros
   Storage: 
/var/lib/systemd/coredump/core.pulseaudio.1001.d834b6de713f4e04816eb5b83e7100a3.11356.1488417855.lz4
   Message: Process 11356 (pulseaudio) of user 1001 dumped core.

Stack trace of thread 11376:
#0  0xb0c6f962 n/a (libsbc.so.1)


GNU gdb (Debian 7.12-6) 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 "arm-linux-gnueabihf".
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/pulseaudio...Reading symbols from 
/usr/lib/debug/.build-id/1b/d03b66bbc1da7b639af9914dd3db452a0905f2.debug...done.
done.
[New LWP 11376]
[New LWP 11356]
[New LWP 11360]
[New LWP 11362]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Core was generated by `pulseaudio -'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0xb0c6f962 in ?? () from /usr/lib/arm-linux-gnueabihf/libsbc.so.1
[Current thread is 1 (Thread 0xb0c64300 (LWP 11376))]
(gdb) 
(gdb) thread apply all bt

Thread 4 (Thread 0xb16ff300 (LWP 11362)):
#0  __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:46
#1  0xb6bdc506 in __GI_ppoll (fds=0x7f619fb0, nfds=2, timeout=, 
timeout@entry=0x0, sigmask=sigmask@entry=0x0) at 
../sysdeps/unix/sysv/linux/ppoll.c:39
#2  0xb6e3f846 in ppoll (__ss=0x0, __timeout=0x0, __nfds=, 
__fds=) at /usr/include/arm-linux-gnueabihf/bits/poll2.h:77
#3  pa_rtpoll_run (p=0x7f5fcad0) at pulsecore/rtpoll.c:314
#4  0xb20672fe in thread_func (userdata=0x7f5f6af8) at 
modules/alsa/alsa-source.c:1516
#5  0xb6df0970 in internal_thread_func (userdata=0x7f5fbd68) at 
pulsecore/thread-posix.c:81
#6  0xb6ce25e4 in start_thread (arg=0x0) at pthread_create.c:335
#7  0xb6be2472 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:86 from 
/lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 3 (Thread 0xb2043300 (LWP 11360)):
#0  __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:46
#1  0xb6bdc506 in __GI_ppoll (fds=0x7f6bf290, nfds=3, timeout=, 
timeout@entry=0x0, sigmask=sigmask@entry=0x0) at 
../sysdeps/unix/sysv/linux/ppoll.c:39
#2  0xb6e3f846 in ppoll (__ss=0x0, __timeout=0x0, __nfds=, 
__fds=) at /usr/include/arm-linux-gnueabihf/bits/poll2.h:77
#3  pa_rtpoll_run (p=0x7f5e85e8) at pulsecore/rtpoll.c:314
#4  0xb20623c8 in thread_func (userdata=0x7f684ca0) at 
modules/alsa/alsa-sink.c:1799
#5  0xb6df0970 in internal_thread_func (userdata=0x7f610cf0) at 
pulsecore/thread-posix.c:81
#6  0xb6ce25e4 in start_thread (arg=0x0) at pthread_create.c:335
#7  0xb6be2472 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:86 from 
/lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 2 (Thread 0xb6f31000 (LWP 11356)):
#0  __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:46
#1  0xb6bdc506 in __GI_ppoll (fds=fds@entry=0x7f62f0c0, nfds=nfds@entry=25, 
timeout=, sigmask=sigmask@entry=0x0)
at ../sysdeps/unix/sysv/linux/ppoll.c:39
#2  0xb6d87940 in ppoll (__ss=0x0, __timeout=, __nfds=25, 
__fds=0x7f62f0c0) at /usr/include/arm-linux-gnueabihf/bits/poll2.h:77
#3  pa_mainloop_poll (m=m@entry=0x7f58ce58) at pulse/mainloop.c:852
#4  0xb6d87dd8 in pa_mainloop_iterate (m=0x7f58ce58, block=, 
retval=0xbea1bf44) at pulse/mainloop.c:926
#5  0xb6d87e5c in pa_mainloop_run (m=0x7f58ce58, 

Bug#856487: pulseaudio: SIGSEGV upon streaming to bluetooth headset

[Linus Lüssing]

Hi Felipe,

Thanks a lot for your quick reply! :)

On Wed, Mar 01, 2017 at 03:12:58PM -0300, Felipe Sateler wrote:
> Did you have the pulseaudio debug packages installed? Please install
> pulseaudio-dbgsym and libpulse-dbgsym.

Nope, I didn't. But looks like there is none available for armhf
(yet)? Is there another way to obtain/install debug packages?
(or should I just try to recompile pulseaudio myself?)

> > Storage part can be found here:
> > http://metameute.de/~tux/bugreport/pulseaudio/core.pulseaudio.1001.ac412473aa4a4c6bb9a7784048ee138c.15991.1488351618.lz4
> 
> This returns 403 forbidden.

Urgh, permissions - fixed, thanks :).

Regards, Linus

Bug#830185: [coccinelle] Fatal errors when running Linux coccicheck

[Linus Lüssing]

Hi Franz,

I'm wondering whether the problem you are having and the
one the batman-adv project has are the same:

https://www.open-mesh.org/issues/303

There too, on Debian Stretch + Sid patching through coccinelle
works fine. Debian Jessie fails.

Franz, do you have the same error when trying to issue your
command with a coccinelle build from the vanilla 1.0.6 git
tag on a Debian Jessie? Does changing any of the ./configure
options change anything for you?

For batman-adv we are currently wondering whether our (and maybe
your issue, too?) might have something to do with the build
options used for the coccinelle 1.0.0~rc22.deb-1 package.

Regards, Linus

Bug#814959: Keyboard mapping broken with Qt5 apps in TightVNC, possibly due to missing XKEYBOARD extension

[Linus Lüssing]

I stumbled over this issue with various Qt5 applications on Debian
Sid, too, and had initially reported my issue here:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818232

Switching the VNC viewer does not seem to help, I tried
xtightvncviewer and krdc.

Not only the TightVNC server, but also the RealVNC one
(vnc4server package) seem to be affected. TigerVNC on the other
hand works like a charm (which is my current workaround for this
issue for now).

Noticeably, on TightVNC and RealVNC, I get this error message,
while on TigerVNC I don't:

"Qt: XKEYBOARD extension not present on the X server."

So looks like James initial investigations lead to the right
direction.

Unfortunately, this report on the Qt bugtracker indicates that it
was closed and deemed "out of scope" and that VNC servers should
implement this XKEYBOARD extension :-( :

https://bugreports.qt.io/browse/QTBUG-44938

This ticket also has some nice explanations why Qt5 has this issue
and Qt4 doesn't (e.g. the preference of libxkbcommon over xlib in
Qt5).

Regards, Linus

Bug#818232: Info received (Bug#818232: Not really a Qt5 bug it seems)

[Linus Lüssing]

Did some further tests and it seems to me that it is this issue:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814959

I'll continue watching and commenting on that one then.

Spoiler: Switching to TigerVNC is a workaround for me for now (vnc4server / 
"RealVNC" seems to have the same issue as TightVNC).

Bug#840504: Acknowledgement (dbus: installation from chroot/systemd-nspawn fails)

[Linus Lüssing]

Sorry, this message does not seem to have put dpkg in a broken
state, just verified with another, new installation where this
message occures too, but dpkg is absolutely fine with it.

Please close this issue for now and sorry for the noise again.

Bug#818232: Not really a Qt5 bug it seems

[Linus Lüssing]

On Sat, Aug 27, 2016 at 12:31:02PM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> reassign 818232 src:qtbase-opensource-src
> forcemerge 814959 818232
> thanks
> 
> It seems this bug is solved with a newer version of TightVNC.

Hi Lisandro,

Sorry for the late reply now. Unfortunately, the issue is still
present for me, even with Qt 5.6.1 instead of 5.5.1 and a recent
tightvncserver (1.3.9-8).

As you suggested, I now tried a different VNC viewer. Switching
from xtightvncviewer (1.3.9-6.5) to krdc (4:4.14.1-1) does not
help, the same weird key swapping happens within krdc. 

While Qt5 applications think the "u-key" is an "m" for instance,
it looks correct in xev, here within xtightvncviewer:

~
KeyPress event, serial 26, synthetic NO, window 0x2c1,
root 0x25, subw 0x0, time 2631956143, (573,420), root:(574,421),
state 0x0, keycode 58 (keysym 0x75, u), same_screen YES,
XLookupString gives 1 bytes: (75) "u"
XmbLookupString gives 1 bytes: (75) "u"
XFilterEvent returns: False

KeyRelease event, serial 26, synthetic NO, window 0x2c1,
root 0x25, subw 0x0, time 2631956782, (573,420), root:(574,421),
state 0x0, keycode 58 (keysym 0x75, u), same_screen YES,
XLookupString gives 1 bytes: (75) "u"
XFilterEvent returns: False
~

Regards, Linus

Bug#836220: Acknowledgement (apt: Upgrading apt from 1.2.13 to 1.3~rc3 fails)

[Linus Lüssing]

For anyone else running into this issue, this following helps as a
workaround:

$ apt-get download apt-utils && apt-get install apt-utils_*.deb && apt-get 
install -f

Regards, Linus

Bug#834633: Info received (Bug#834633: Acknowledgement (gpg: signing failed / agent_genkey failed: Operation cancelled))

[Linus Lüssing]

With some help from IRC the problem could be narrowed down to
pinentry. My setup so far involved a VNC session and the only
pinentry package installed was "pinentry-gnome3". What works for
me is pinentry-gtk2, for instance.

Using VNC:
* pinentry-gnome3: "Operation cancelled" (why?)
* pinentry-gtk2: works!
* pinentry-qt: Other, VNC+qt4 specific bug
* pinentry-curses: "Permission denied" (why?)

Using ssh:
* pinentry-gnome3: Permission denied (obviously,needs X11)
* pinentry-gtk2: Permission denied (obviously, needs X11)
* pinentry-qt: Permission denied (obviously, needs X11)
* pinentry-curses: Permission denied (why?) 

Using ssh with X-forwarding (ssh -X):
* pinentry-gnome3: Operation cancelled (why?)
* pinentry-gtk2: works!
* pinentry-qt:  works!
* pinentry-curses: Permission denied (why?)


So I'll be using pinentry-gtk2 for now which reduces the severity
of this bug for me. But the error message gnupg displays is a
little confusing and does not indicate to the user that s/he
should maybe try installing an alternative (non-broken?) pinentry
package.

Regards, Linus


PS: And with switching to pinentry-gtk2 I also had to add a
"set pgp_use_gpg_agent=yes" to my muttrc to avoid being asked for
a password twice (once within mutt and once in the pop-up).

Bug#834633: Acknowledgement (gpg: signing failed / agent_genkey failed: Operation cancelled)

[Linus Lüssing]

Actually, seems like the upgrade of the gnupg package from
1.4 to 2.1 is the issue (gnupg:armhf (1.4.20-6, 2.1.14-5) ).

Just reinstalled the old 1.4.20-6 version for the gnupg package
and things work nicely for me again.

Anyone having an idea why gnupg2 might fail for me?

Regards, Linus

Bug#818232: Acknowledgement (qgo: Unable to type via VNC, keys not matching)

[Linus Lüssing]

Okay, happens with other Qt5 applications, like musescore, dolphin
or ktimer, too. Qt4 applications are unaffected (for instance
mumble).

This report should probably be moved to libqt5gui5 then?

Bug#814454: reportbug: Crash when trying to configure non-ASCII characters for realname via CLI

[Linus Lüssing]

Hi Sandro,

On Fri, Mar 04, 2016 at 09:39:53PM +, Sandro Tosi wrote:
> I've uploaded to backports version 6.6.6 of reportbug which should
> address this bug: please install that and report back if that's fixed.

Just tried and 6.6.6 works like a charm on the same device, issue
seems to be fixed in there :).

Cheers, Linus

Bug#814542: vnstat not starting on boot on device without Real-time Clock

[Linus Lüssing]

Package: vnstat
Version: 1.12-2
Severity: important

Dear Maintainer,

On an Alix board without an RTC I am currently having trouble to get vnstat 
running
on boot, I always get the following error:

-
$ systemctl status vnstat
● vnstat.service - vnStat network traffic monitor
   Loaded: loaded (/lib/systemd/system/vnstat.service; enabled)
   Active: failed (Result: exit-code) since Sa 2000-01-01 01:02:07 CET; 16 
years 1 months ago
 Docs: man:vnstatd(1)
   man:vnstat(1)
   man:vnstat.conf(5)
  Process: 466 ExecStart=/usr/sbin/vnstatd -n (code=exited, status=1/FAILURE)
 Main PID: 466 (code=exited, status=1/FAILURE)

Jan 01 01:02:06 nm-alix systemd[1]: Started vnStat network traffic monitor.
Jan 01 01:02:06 nm-alix vnstatd[466]: Info: Monitoring: eth0 (100 Mbit) eth1 
(100 Mbit) ppp0 (100 Mbit)
Jan 01 01:02:06 nm-alix vnstatd[466]: Error: Interface "eth0" has previous 
update date too much in the future, exiting. (1455245147 / 946684926)
Jan 01 01:02:07 nm-alix systemd[1]: vnstat.service: main process exited, 
code=exited, status=1/FAILURE
Jan 01 01:02:07 nm-alix systemd[1]: Unit vnstat.service entered failed state.
-

Starting vnstat manually ("$ systemctl start vnstat") works as at that time NTP 
has fetched
the correct time for me.

On embedded devices it is rather common to not have an RTC and with
ARM based devices running Debian on the rise, I thought I'd mark this
bug as "important".


I guess either vnstat should retry instead of exiting. And/or maybe the
neat, new dependancy system available thanks to systemd could be used.
The mysqld unit does something like that, e.g. units depending on it
will be started not after mysqld has started, but once mysqld reports
being ready to receive queries. This is done through 
"ExecStartPost=/usr/libexec/mysqld-wait-ready" in the mysqld unit.
Maybe something like that could be done with NTP and vnstat too?

A quick and dirty solution would be to simply add the line "Restart=on-failure"
to the vnstat unit, I guess.

Regards, Linus


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

Kernel: Linux 3.16.0-4-586
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages vnstat depends on:
ii  adduser  3.113+nmu3
ii  init-system-helpers  1.22
ii  libc62.19-18+deb8u2

vnstat recommends no packages.

Versions of packages vnstat suggests:
pn  vnstati  

-- no debconf information

Bug#814542: vnstat not starting on boot on device without Real-time Clock

[Linus Lüssing]

On Fri, Feb 12, 2016 at 07:58:35PM +0100, Linus Lüssing wrote:
> A quick and dirty solution would be to simply add the line 
> "Restart=on-failure"
> to the vnstat unit, I guess.

PS: And maybe, if that solution were chosen, adding a "RestartSec=10" there too
for a 10 seconds restart wait instead of the default 100ms wait.

Bug#811461: libqtgui4: Blank windows with "non-default" users

[Linus Lüssing]

On Tue, Jan 19, 2016 at 12:23:25PM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Control: tag -1 moreinfo
> 
> Do you see any strange messages in ~/.xsession-errors ?

Hm, no errors in there.

> 
> I also don't fully understand what you do. For what I read I think you start 
> an X session by running Xtightvnc with user A and then you want to run some 
> Qt4 tool with user B, right?

Correct :).

> 
> Anyways Qt4 is in security fixes only mode, so I won't get help from upstream 
> to solve this.
> 
> If you can also try to see what happens with Qt5 apps.

Qt5 apps seem to run fine too. Just tested dolphin, musescore and
ktimer. So seems to be just Qt4 related.

Cheers, Linus

Bug#803216: closed by Markus Koschany <a...@debian.org> (Bug#803216: fixed in torus-trooper 0.22.dfsg1-10)

[Linus Lüssing]

On Thu, Nov 12, 2015 at 06:24:10PM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the torus-trooper package:
> 
> #803216: torus-trooper: segfault on startup in src/abagames/tt/barrage.d:111
> 
> It has been closed by Markus Koschany .

Thanks Markus, works great now :).

Bug#803216: Acknowledgement (torus-trooper: segfault on startup in src/abagames/tt/barrage.d:111)

[Linus Lüssing]

Btw., if I simply remove the crashing line, the check, then
everything starts fine. Can it actually happen that this API
returns the same file name more than once for a specific
directory listing? Could this check be unnecessary, maybe?

Cheers, Linus


PS: I also don't understand why the "parser[dirName] = null"
assignment is needed. But I'm probably simply overlooking
something, it's the first time I'm looking at code written in D
:).


On Wed, Oct 28, 2015 at 01:42:06AM +, Debian Bug Tracking System wrote:
> Thank you for filing a new Bug report with Debian.
> 
> This is an automatically generated reply to let you know your message
> has been received.
> 
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
> 
> As you requested using X-Debbugs-CC, your message was also forwarded to
>   linus.luess...@c0d3.blue
> (after having been given a Bug report number, if it did not have one).
> 
> Your message has been sent to the package maintainer(s):
>  Debian Games Team 
> 
> If you wish to submit further information on this problem, please
> send it to 803...@bugs.debian.org.
> 
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
> 
> -- 
> 803216: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803216
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

Bug#803216: torus-trooper: segfault on startup in src/abagames/tt/barrage.d:111

[Linus Lüssing]

Package: torus-trooper
Version: 0.22.dfsg1-9
Severity: grave
Justification: renders package unusable

Hi,

I am currently unable to start torus-trooper as it crashes with a segmentation 
fault. I have downloaded the source package (apt-get source torus-trooper), 
rebuilt it (dpkg-buildpackage) and started it with gdb. The backtrace shows a 
crash in src/abagames/tt/barrage.d:111. See the attached gdb output for details.

Let me know if you need any further information.

Cheers, Linus


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

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

Versions of packages torus-trooper depends on:
ii  libbulletml0v50.0.6-6.1
ii  libc6 2.19-22
ii  libgcc1   1:5.2.1-22
ii  libgl1-mesa-glx [libgl1]  10.6.3-1
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libsdl-mixer1.2   1.2.12-11+b1
ii  libsdl1.2debian   1.2.15-11
ii  torus-trooper-data0.22.dfsg1-9

torus-trooper recommends no packages.

torus-trooper suggests no packages.

-- no debconf information
GNU gdb (Debian 7.10-1) 7.10
Copyright (C) 2015 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 torus-trooper...done.
(gdb) run
Starting program: /tmp/tt-deb/torus-trooper-0.22.dfsg1/torus-trooper 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe5283700 (LWP 26362)]
[Thread 0x7fffe5283700 (LWP 26362) exited]
[New Thread 0x7fffe5283700 (LWP 26363)]

Program received signal SIGSEGV, Segmentation fault.
0x00418b32 in abagames.tt.barrage.BarrageManager.getInstance(immutable(char)[], immutable(char)[]) (
fileName=..., dirName=...) at src/abagames/tt/barrage.d:111
111	if (!parser[dirName][fileName]) {
(gdb) bt
#0  0x00418b32 in abagames.tt.barrage.BarrageManager.getInstance(immutable(char)[], immutable(char)[])
(fileName=..., dirName=...) at src/abagames/tt/barrage.d:111
#1  abagames.tt.barrage.BarrageManager.load() () at src/abagames/tt/barrage.d:105
#2  0x00427a74 in abagames.tt.gamemanager.GameManager.init() (this=...)
at src/abagames/tt/gamemanager.d:63
#3  0x00427364 in abagames.util.sdl.mainloop.MainLoop.initFirst() (this=...)
at src/abagames/util/sdl/mainloop.d:53
#4  abagames.util.sdl.mainloop.MainLoop.loop() (this=...) at src/abagames/util/sdl/mainloop.d:79
#5  0x004291dc in abagames.tt.boot.boot(immutable(char)[][]) (args=...) at src/abagames/tt/boot.d:86
#6  0x00434e7f in __lambda1 (this=0x7fffe170)
at ../../../../src/libphobos/libdruntime/rt/dmain2.d:411
#7  0x00434faf in rt.dmain2._d_run_main(int, char**, extern(C) int(char[][]) function*).tryExec(scope void() delegate) (this=this@entry=0x7fffe170, dg=...)
at ../../../../src/libphobos/libdruntime/rt/dmain2.d:386
#8  0x00435359 in runAll (this=0x7fffe170)
at ../../../../src/libphobos/libdruntime/rt/dmain2.d:411
#9  0x00434faf in rt.dmain2._d_run_main(int, char**, extern(C) int(char[][]) function*).tryExec(scope void() delegate) (this=this@entry=0x7fffe170, dg=...)
at ../../../../src/libphobos/libdruntime/rt/dmain2.d:386
#10 0x00435136 in _d_run_main (argc=1, argv=0x7fffe2b8, mainFunc=)
at ../../../../src/libphobos/libdruntime/rt/dmain2.d:419
#11 0x764f1b45 in __libc_start_main (main=0x406c20 , argc=1, argv=0x7fffe2b8, 
init=, fini=, rtld_fini=, stack_end=0x7fffe2a8)
at libc-start.c:287
#12 0x00407eb3 in _start ()
(gdb) quit
A debugging session is active.

	Inferior 1 [process 26358] will be killed.

Quit anyway? (y or n) y

Bug#744725: busybox: wget is appending instead of replacing with --header

[Linus Lüssing]

Package: busybox
Version: 1:1.22.0-5
Severity: normal

The following command fails for me:

---
$ busybox wget --header 'Host: 1.updates.services.ffhl' 
http://luebeck.freifunk.net/stable/sysupgrade/gluon-ffhl-0.4-tp-link-tl-mr3420-v1-sysupgrade.bin;
Connecting to luebeck.freifunk.net (141.83.153.180:80)
wget: server returned error: HTTP/1.1 404 Not Found
---

While with GNU Wget 1.15 it works just fine:

---
wget --header 'Host: 1.updates.services.ffhl' 
http://luebeck.freifunk.net/stable/sysupgrade/gluon-ffhl-0.4-tp-link-tl-mr3420-v1-sysupgrade.bin;

--2014-04-13 23:58:26--  
http://luebeck.freifunk.net/stable/sysupgrade/gluon-ffhl-0.4-tp-link-tl-mr3420-v1-sysupgrade.bin
Resolving luebeck.freifunk.net (luebeck.freifunk.net)... 141.83.153.180, 
2001:638:70a:b153:6e62:6dff:fe82:ec06
Connecting to luebeck.freifunk.net (luebeck.freifunk.net)|141.83.153.180|:80... 
connected.
HTTP request sent, awaiting response... 200 OK
Length: 3407876 (3.2M) [application/octet-stream]
Saving to: ‘gluon-ffhl-0.4-tp-link-tl-mr3420-v1-sysupgrade.bin.3’

 0% [  ] 
28,936  10.1KB/s ^C
---

Looking at the HTTP Get message with wireshark it seems that
busybox-wget is keeping the original Host: luebeck.freifunk.net and
only appends Host: 1.updates.services.ffhl. While GNU-wget is
replacing the original http host field which seems to make more sense
from a user's perspective.

Cheers, Linus


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

Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages busybox depends on:
ii  libc6  2.18-4

busybox recommends no packages.

busybox 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#733923: x11-xkb-utils: swap_lalt_lwin not working anymore since last update

[Linus Lüssing]

Package: x11-xkb-utils
Version: 7.7+1
Severity: normal

Hi,

I did a dist-upgrade a couple of days ago and since then I'm not able to
swap the left win and alt keys anymore. I've always been using the
following command:

---
setxkbmap -layout de,de -variant neo,basic -option -option 
grp:ctrls_toggle,altwin:swap_lalt_lwin
---

The keyboard layout/variant part works great, however the
swap_lalt_lwin seems to do nothing now.

Cheers, Linus


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

Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages x11-xkb-utils depends on:
ii  libc62.17-97
ii  libx11-6 2:1.6.2-1
ii  libxaw7  2:1.0.11-1
ii  libxkbfile1  1:1.0.8-1
ii  libxt6   1:1.1.4-1

x11-xkb-utils recommends no packages.

x11-xkb-utils 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#734010: qgo: Servers in Connect window vanished

[Linus Lüssing]

Package: qgo
Version: 2.0~git-20131123-1
Severity: grave
Justification: renders package unusable

Hi,

Since the upgrade of qgo a couple of days ago, version
2.0~git-20130914-1 to 2.0~git-20131123-1, I'm not able to connect to any
Go server anymore. After clicking on Connect the list of servers is
just empty now.

Cheers, Linus


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

Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages qgo depends on:
ii  libc6 2.17-97
ii  libgcc1   1:4.8.2-11
ii  libgl1-mesa-glx [libgl1]  9.2.2-1
ii  libpulse0 4.0-6+b1
ii  libqt5core5   5.1.1+dfsg-6
ii  libqt5gui55.1.1+dfsg-6
ii  libqt5multimedia5 5.1.1-2
ii  libqt5network55.1.1+dfsg-6
ii  libqt5widgets55.1.1+dfsg-6
ii  libstdc++64.8.2-11

qgo recommends no packages.

Versions of packages qgo suggests:
ii  gnugo  3.8-7

-- 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#734010: qgo: Servers in Connect window vanished

[Linus Lüssing]

Ok, I figured that it's not actually the servers having vanished.
Instead the layout of the Connect menu changed.

However, my credentials on IGS were deleted in qgo and I had to
readd them manually in the new menu (luckily I could still
remember them).

A migration path would have been nicer.


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

Bug#734016: qgo: segmentation fault on Talk via double click on name

[Linus Lüssing]

Package: qgo
Version: 2.0~git-20131123-1
Severity: normal


When trying to open a talk via a double click on a name in the players
list, qgo crashes with a segmentation fault.

Opening a talk via a right click and selecting Talk works fine though.

Here's a backtrace created via gdb:


---
$ gdb qgo
GNU gdb (GDB) 7.6.1 (Debian 7.6.1-1)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
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.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/games/qgo...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/games/qgo
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need set solib-search-path or set sysroot?
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
[New Thread 0x7fffeb065700 (LWP 7258)]
Error:Key MDSW added to modifier map for multiple modifiers; Using 
Mod3, ignoring Mod5
Fontconfig warning: /etc/fonts/conf.d/65-ttf-sil-andika.conf, line 14: Having 
multiple values in test isn't supported and may not work as expected
Fontconfig warning: /etc/fonts/conf.d/65-ttf-sil-andika.conf, line 32: Having 
multiple family in alias isn't supported and may not work as expected
Fontconfig warning: /etc/fonts/conf.d/65-ttf-sil-andika.conf, line 32: Having 
multiple family in alias isn't supported and may not work as expected
Fontconfig warning: /etc/fonts/conf.d/65-ttf-sil-andika.conf, line 32: Having 
multiple family in alias isn't supported and may not work as expected
Fontconfig warning: /etc/fonts/conf.d/65-ttf-sil-andika.conf, line 32: Having 
multiple family in alias isn't supported and may not work as expected
Fontconfig warning: /etc/fonts/conf.d/65-ttf-sil-andika.conf, line 32: Having 
multiple family in alias isn't supported and may not work as expected
Fontconfig warning: /etc/fonts/conf.d/65-ttf-sil-andika.conf, line 32: Having 
multiple family in alias isn't supported and may not work as expected
Fontconfig warning: /etc/fonts/conf.d/65-ttf-sil-andika.conf, line 32: Having 
multiple family in alias isn't supported and may not work as expected
Home Path : /new-home/linus
Current Path : /new-home/linus
defaultServiceProvider::requestService(): no service found for - 
org.qt-project.qt.mediaplayer
Connecting to igs.joyjoy.net ...

[New Thread 0x7fffdc66e700 (LWP 7259)]
rank spread : NR - 9p
Login found

:10 ??
1 1


Password prompt or 1 1 found
sendText: toggle looking  false

sendText: toggle open  false

sendText: join 0

Joining 0
Ready!

Creating Talk for

Program received signal SIGSEGV, Segmentation fault.
0x761ea12b in operator==(QString const, QString const) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
(gdb) bt
#0  0x761ea12b in operator==(QString const, QString const) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7731ea65 in QLabel::setText(QString const) () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#2  0x0051665b in ?? ()
#3  0x00516910 in ?? ()
#4  0x0051069f in ?? ()
#5  0x005607c5 in ?? ()
#6  0x76348226 in QMetaObject::activate(QObject*, int, int, void**) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x77404955 in QAbstractItemView::doubleClicked(QModelIndex const) 
()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x77412855 in 
QAbstractItemView::mouseDoubleClickEvent(QMouseEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x77221d84 in QWidget::event(QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x7731b81e in QFrame::event(QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x774122eb in QAbstractItemView::viewportEvent(QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x763228e3 in 
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x771e7f2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) 
()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x771ed89b in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x763226bd in QCoreApplication::notifyInternal(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x771ebbc1 in QApplicationPrivate::sendMouseEvent(QWidget*, 
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointerQWidget, bool) () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x7723d86f in ?? () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x7723f583 in ?? () from 

Bug#733846: pidgin: crash on startup: illegal hardware instruction / invalid opcode

[Linus Lüssing]

On Wed, Jan 01, 2014 at 10:01:05PM -0500, Ari Pollak wrote:
 It seems unlikely that pidgin is at fault here, given that it hasn't
 been updated in almost a year. Do you happen to have
 gstreamer0.10-buzztard installed? Does this still happen if you remove it?

Yes, I had it installed and removing it (which automatically
removed the package buzztard, too) helped :). No more crashes now,
pidgin works fine again.


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

Bug#733846: pidgin: crash on startup: illegal hardware instruction / invalid opcode

[Linus Lüssing]

Package: pidgin
Version: 2.10.7-2+b1
Severity: grave
Justification: renders package unusable

Hi,

Since my last dist-upgrade two days ago I'm not able to start pidgin
anymore, the console returns the following:

---
$ pidgin
zsh: illegal hardware instruction  pidgin
---

And dmesg says:
---
[31793.953373] traps: pidgin[21225] trap invalid opcode ip:7fab94540348 
sp:7fff3bbb8260 error:0 in libbuzztard-core.so.0.6.0[7fab94511000+59000]
---

Cheers, Linus


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

Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages pidgin depends on:
ii  gconf2  3.2.6-1
ii  libatk1.0-0 2.10.0-2
ii  libc6   2.17-97
ii  libcairo2   1.12.16-2
ii  libdbus-1-3 1.6.18-2
ii  libdbus-glib-1-20.100.2-1
ii  libfontconfig1  2.11.0-2
ii  libfreetype62.5.2-1
ii  libgdk-pixbuf2.0-0  2.28.2-1+b1
ii  libglib2.0-02.36.4-1
ii  libgstreamer0.10-0  0.10.36-1.2
ii  libgtk2.0-0 2.24.22-1
ii  libgtkspell02.0.16-1
ii  libice6 2:1.0.8-2
ii  libpango-1.0-0  1.36.0-1+b1
ii  libpangocairo-1.0-0 1.36.0-1+b1
ii  libpangoft2-1.0-0   1.36.0-1+b1
ii  libpurple0  2.10.7-2+b1
ii  libsm6  2:1.2.1-2
ii  libx11-62:1.6.2-1
ii  libxml2 2.9.1+dfsg1-3
ii  libxss1 1:1.2.2-1
ii  perl-base [perlapi-5.18.1]  5.18.1-5
ii  pidgin-data 2.10.7-2

Versions of packages pidgin recommends:
ii  gstreamer0.10-plugins-base  0.10.36-1.1
ii  gstreamer0.10-plugins-good  0.10.31-3+nmu2

Versions of packages pidgin suggests:
ii  libsqlite3-0  3.8.2-1

-- 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#732105: tor: Crash on startup: Error in `tor': free(): invalid pointer: 0x00007f0ad9db532b

[Linus Lüssing]

Hi!

And thanks for the quick response.

On Sat, Dec 14, 2013 at 10:46:28AM +0100, Peter Palfrader wrote:
 Linus Lüssing schrieb am Samstag, dem 14. Dezember 2013:
 
  Version: 0.2.3.25-1
 
 What can you tell me about your system that would be different from all
 the others?

No clue yet. It's Debian unstable, 64bit both user space and
kernel space wise:
$ dpkg --print-architecture
amd64

Though i386 was added through multiarch support, too:
$ dpkg --print-foreign-architectures
i386

Also, I'm having this issue for a few weeks if not months now. A
few months ago everything was working fine. No idea what has
happened between that yet, a new Tor or related library version
installed via apt-get dist-upgrade is the only guess I'm having.

Btw., the Tor browser bundle as provided by torproject.org
(tor-browser-gnu-linux-x86_64-2.3.25-16-dev-en-US) starts up fine.

I'm going to check whether running Tor via debootstrap/chroot
works later.

 
  $ tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc
  ... then I'm getting the following error message:
  Error in `tor': free(): invalid pointer: 0x7f0ad9db532b
 
 Is this from a root shell?  How does your torrc look like?

It's invoked via sudo. Invoking it from a complete root shell
(bash) doesn't make a difference, though.

Ah! Thought --defaults-torrc would be the complete torrc in use.
Invoking things with this command:

$ sudo tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f 
/etc/tor/torrc-fg

... with /etc/tor/torrc-fg having this single line:
RunAsDaemon 0

... doesn't make a difference either.

 
  For the complete command line output, including a backtrace (the debug
  symbols seem to be missing even though I've installed tor-dbg?), see the
  attached log.
 
 How did you try to produce the backtrace?

I'm not trying, it just happens every time :).

Cheers, Linus


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

Bug#732105: tor: Crash on startup: Error in `tor': free(): invalid pointer: 0x00007f0ad9db532b

[Linus Lüssing]

On Sat, Dec 14, 2013 at 11:42:42AM +0100, Peter Palfrader wrote:
For the complete command line output, including a backtrace (the debug
symbols seem to be missing even though I've installed tor-dbg?), see the
attached log.
   
   How did you try to produce the backtrace?
  
  I'm not trying, it just happens every time :).
 
 No, the crashes happen.  The bt doesn't just magically appear, does it?  :)
 

Hm, right, usually not. But it's not me trying to produce the
backtrace :). I'm not invoking gdb or some fancy, custom LD_PRELOAD
stuff if that's what you mean. Maybe it's a new feature of libc or
something like that?

But now that you are mentioning it, that probably explains the
missing function names. I'm attaching an additional backtrace,
this time created via gdb.

And here's the output of an ldd:
$ ldd /usr/sbin/tor
linux-vdso.so.1 (0x7fff7a5fe000)
libz.so.1 = /lib/x86_64-linux-gnu/libz.so.1 (0x7f9abbe7a000)
libm.so.6 = /lib/x86_64-linux-gnu/libm.so.6 (0x7f9abbb7c000)
libevent-2.0.so.5 = /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 
(0x7f9abb934000)
libssl.so.1.0.0 = /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0 
(0x7f9abb6d5000)
libcrypto.so.1.0.0 = /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 
(0x7f9abb2e2000)
librt.so.1 = /lib/x86_64-linux-gnu/librt.so.1 (0x7f9abb0d9000)
libdl.so.2 = /lib/x86_64-linux-gnu/libdl.so.2 (0x7f9abaed5000)
libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f9abab29000)
libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f9aba90c000)
/lib64/ld-linux-x86-64.so.2 (0x7f9abc44c000)

(and running sudo /usr/sbin/tor --defaults-torrc ... yields the
same crash, so all the tor binaries invoked so far should have
been /usr/sbin/tor as it should be, so messed up PATH variables
can't be the issue either)

Cheers, Linus
$ sudo gdb --args tor --defaults-torrc 
/usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc-fg
GNU gdb (GDB) 7.6.1 (Debian 7.6.1-1)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
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.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/sbin/tor...Reading symbols from 
/usr/lib/debug/usr/sbin/tor...(no debugging symbols found)...done.
(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/sbin/tor --defaults-torrc 
/usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc-fg
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need set solib-search-path or set sysroot?
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
Dec 14 12:18:01.184 [notice] Tor v0.2.3.25 (git-3fed5eb096d2d187) running on 
Linux.
Dec 14 12:18:01.184 [notice] Tor can't help you if you use it wrong! Learn how 
to be safe at https://www.torproject.org/download/download#warning
Dec 14 12:18:01.184 [notice] Read configuration file 
/usr/share/tor/tor-service-defaults-torrc.
Dec 14 12:18:01.185 [notice] Read configuration file /etc/tor/torrc-fg.
Dec 14 12:18:01.196 [notice] We were compiled with headers from version 
2.0.19-stable of Libevent, but we're using a Libevent library that says it's 
version 2.0.21-stable.
Dec 14 12:18:01.196 [notice] Initialized libevent version 2.0.21-stable using 
method epoll (with changelist). Good.
Dec 14 12:18:01.196 [notice] Opening Socks listener on 127.0.0.1:9050
Dec 14 12:18:01.402 [notice] Opening Control listener on /var/run/tor/control
*** Error in `/usr/sbin/tor': free(): invalid pointer: 0x7577d32b ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x7aa16)[0x768eea16]
/lib/x86_64-linux-gnu/libc.so.6(+0x7b793)[0x768ef793]
/usr/sbin/tor(+0x178d2)[0x5556b8d2]
/usr/sbin/tor(+0x5ff7c)[0x555b3f7c]
/usr/sbin/tor(+0x188c5)[0x5556c8c5]
/usr/sbin/tor(+0x18b11)[0x5556cb11]
/usr/sbin/tor(+0x18c8f)[0x5556cc8f]
/usr/sbin/tor(+0x19082)[0x5556d082]
/usr/sbin/tor(+0x1e9ae)[0x555729ae]
/usr/sbin/tor(+0x15809)[0x55569809]
/usr/sbin/tor(+0x1706e)[0x5556b06e]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x76895995]
/usr/sbin/tor(+0x119fd)[0x555659fd]
=== Memory map: 
4000-556cb000 r-xp  fe:18 302841 
/usr/sbin/tor
558ca000-558cd000 r--p 00176000 fe:18 302841 
/usr/sbin/tor
558cd000-558d3000 rw-p 00179000 fe:18 302841 
/usr/sbin/tor
558d3000-560aa000 rw-p  00:00 0  [heap]
7545a000-7546f000 r-xp  fe:18 647880 

Bug#732105: tor: Crash on startup: Error in `tor': free(): invalid pointer: 0x00007f0ad9db532b

[Linus Lüssing]

On Sat, Dec 14, 2013 at 12:32:38PM +0100, Peter Palfrader wrote:
  (gdb)
 
 OOI, can you move away all the files in /var/lib/tor and try again?
 
 If that helps, I'd be really interested in the contents of these,
 assuming you don't have any private keys or other privileged data there.

Moving the folder away helps. I could narrow the issue down to my
/var/lib/tor/cached-microdescs:

https://metameute.de/~tux/bugreport/debian/732105/cached-microdescs.xz

Cheers, Linus


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

Bug#732105: tor: Crash on startup: Error in `tor': free(): invalid pointer: 0x00007f0ad9db532b

[Linus Lüssing]

Package: tor
Version: 0.2.3.25-1
Severity: grave
Justification: renders package unusable

Hi,

When trying to start Tor with this command, so starting it with the
Debian default torrc:

$ tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc

... then I'm getting the following error message:

Error in `tor': free(): invalid pointer: 0x7f0ad9db532b

For the complete command line output, including a backtrace (the debug
symbols seem to be missing even though I've installed tor-dbg?), see the
attached log.

Cheers, Linus


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

Kernel: Linux 3.11-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages tor depends on:
ii  adduser 3.113+nmu3
ii  libc6   2.17-95
ii  libevent-2.0-5  2.0.21-stable-1
ii  libssl1.0.0 1.0.1e-4
ii  lsb-base4.1+Debian12
ii  zlib1g  1:1.2.8.dfsg-1

Versions of packages tor recommends:
ii  logrotate3.8.6-1
ii  tor-geoipdb  0.2.3.25-1
ii  torsocks 1.3-3

Versions of packages tor suggests:
pn  apparmor-utils none
pn  mixmaster  none
ii  privoxy3.0.21-1
ii  socat  1.7.2.2-1
pn  tor-armnone
pn  xul-ext-torbutton  none

-- Configuration Files:
/etc/default/tor changed [not included]
/etc/tor/torrc changed [not included]

-- debconf-show failed
$ tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc
Dec 14 04:28:30.938 [notice] Tor v0.2.3.25 (git-3fed5eb096d2d187) running on 
Linux.
Dec 14 04:28:30.938 [notice] Tor can't help you if you use it wrong! Learn how 
to be safe at https://www.torproject.org/download/download#warning
Dec 14 04:28:30.938 [notice] Read configuration file 
/usr/share/tor/tor-service-defaults-torrc.
Dec 14 04:28:30.938 [notice] Read configuration file /etc/tor/torrc.
Dec 14 04:28:30.960 [notice] We were compiled with headers from version 
2.0.19-stable of Libevent, but we're using a Libevent library that says it's 
version 2.0.21-stable.
Dec 14 04:28:30.960 [notice] Initialized libevent version 2.0.21-stable using 
method epoll (with changelist). Good.
Dec 14 04:28:30.960 [notice] Opening Socks listener on 127.0.0.1:9050
Dec 14 04:28:30.961 [notice] Opening DNS listener on 127.0.0.1:53535
Dec 14 04:28:30.961 [notice] Opening Transparent pf/netfilter listener on 
127.0.0.1:9040
Dec 14 04:28:30.962 [notice] Opening Control listener on /var/run/tor/control
*** Error in `tor': free(): invalid pointer: 0x7f0ad9db532b ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x7aa16)[0x7f0adaf26a16]
/lib/x86_64-linux-gnu/libc.so.6(+0x7b793)[0x7f0adaf27793]
tor(+0x178d2)[0x7f0adc64e8d2]
tor(+0x5ff7c)[0x7f0adc696f7c]
tor(+0x188c5)[0x7f0adc64f8c5]
tor(+0x18b11)[0x7f0adc64fb11]
tor(+0x18c8f)[0x7f0adc64fc8f]
tor(+0x19082)[0x7f0adc650082]
tor(+0x1e9ae)[0x7f0adc6559ae]
tor(+0x15809)[0x7f0adc64c809]
tor(+0x1706e)[0x7f0adc64e06e]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f0adaecd995]
tor(+0x119fd)[0x7f0adc6489fd]
=== Memory map: 
7f0ad9a92000-7f0ad9aa7000 r-xp  fe:18 647880 
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f0ad9aa7000-7f0ad9ca7000 ---p 00015000 fe:18 647880 
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f0ad9ca7000-7f0ad9ca8000 rw-p 00015000 fe:18 647880 
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f0ad9ca8000-7f0ada156000 r--p  fe:16 921098 
/var/lib/tor/cached-microdescs
7f0ada156000-7f0ada357000 rw-p  00:00 0
7f0ada458000-7f0ada464000 r-xp  fe:18 647974 
/lib/x86_64-linux-gnu/libnss_files-2.17.so
7f0ada464000-7f0ada663000 ---p c000 fe:18 647974 
/lib/x86_64-linux-gnu/libnss_files-2.17.so
7f0ada663000-7f0ada664000 r--p b000 fe:18 647974 
/lib/x86_64-linux-gnu/libnss_files-2.17.so
7f0ada664000-7f0ada665000 rw-p c000 fe:18 647974 
/lib/x86_64-linux-gnu/libnss_files-2.17.so
7f0ada665000-7f0ada66f000 r-xp  fe:18 647976 
/lib/x86_64-linux-gnu/libnss_nis-2.17.so
7f0ada66f000-7f0ada86e000 ---p a000 fe:18 647976 
/lib/x86_64-linux-gnu/libnss_nis-2.17.so
7f0ada86e000-7f0ada86f000 r--p 9000 fe:18 647976 
/lib/x86_64-linux-gnu/libnss_nis-2.17.so
7f0ada86f000-7f0ada87 rw-p a000 fe:18 647976 
/lib/x86_64-linux-gnu/libnss_nis-2.17.so
7f0ada87-7f0ada885000 r-xp  fe:18 647970 
/lib/x86_64-linux-gnu/libnsl-2.17.so
7f0ada885000-7f0adaa84000 ---p 00015000 fe:18 647970 
/lib/x86_64-linux-gnu/libnsl-2.17.so
7f0adaa84000-7f0adaa85000 r--p 00014000 fe:18 647970 
/lib/x86_64-linux-gnu/libnsl-2.17.so
7f0adaa85000-7f0adaa86000 rw-p 00015000 fe:18 

Bug#730804: qgo: segmentation fault on Error: connection closed by host

[Linus Lüssing]

Package: qgo
Version: 2.0~git-20130914-1
Followup-For: Bug #730804


And here's a calltrace gathered via gdb. It's probably not much use without 
debugging symbols in qgo, but well, attaching it anyways:

---
[...]
Not local game.

ERROR: unknown Error...
Socket Error

onConnectionError
Destroying IGS connection
Disconnecting...
Deconstructing room

Program received signal SIGSEGV, Segmentation fault.
0x004a3150 in ?? ()
(gdb) bt
#0  0x004a3150 in ?? ()
#1  0x00484be4 in ?? ()
#2  0x763491e4 in QObject::event(QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x771e6f1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) 
()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#4  0x771ec006 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#5  0x7632286d in QCoreApplication::notifyInternal(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x76368f3d in QTimerInfoList::activateTimers() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x763693f1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x73ed1ea6 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x73ed21f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x73ed229c in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7636971c in 
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x763215bb in 
QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x76327b41 in QCoreApplication::exec() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00426e0f in ?? ()
#15 0x750c7995 in __libc_start_main (main=0x426cf2, argc=1, 
ubp_av=0x7fffdf88,
init=optimized out, fini=optimized out, rtld_fini=optimized out, 
stack_end=0x7fffdf78)
at libc-start.c:276
#16 0x0041b4c9 in ?? ()
(gdb)

---

Cheers, Linus


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

Kernel: Linux 3.11-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages qgo depends on:
ii  libc6 2.17-95
ii  libgcc1   1:4.8.2-2
ii  libgl1-mesa-glx [libgl1]  9.2.2-1
ii  libpulse0 4.0-6+b1
ii  libqt5core5   5.1.1+dfsg-5
ii  libqt5gui55.1.1+dfsg-5
ii  libqt5multimedia5 5.1.1-1
ii  libqt5network55.1.1+dfsg-5
ii  libqt5widgets55.1.1+dfsg-5
ii  libstdc++64.8.2-2

qgo recommends no packages.

Versions of packages qgo suggests:
ii  gnugo  3.8-6

-- 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#730804: qgo: segmentation fault on Error: connection closed by host

[Linus Lüssing]

Package: qgo
Version: 2.0~git-20130914-1
Severity: important

Hi,

a few times I've head the issue of qgo crashing:

-
[...]

15 255(W): B5

sendText: A4 158

Not local game.

Not local game.

ERROR: connection closed by host ...
Socket Error

onConnectionError
Destroying IGS connection
Disconnecting...
Deconstructing room
zsh: segmentation fault  qgo
-

So at some point when it was my turn I wasn't able to do a move anymore, 
clicking did not do anything in the GUI. A few seconds later (something between 
30 to 60 seconds, so around the TCP connection timeout?), qgo crashed with a 
segmentation fault.

I'm not sure, it seems like either my opponent has left the game or my wifi 
connection was failing for a few seconds while playing against someone else on 
IGS.

Cheers, Linus


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

Kernel: Linux 3.11-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages qgo depends on:
ii  libc6 2.17-95
ii  libgcc1   1:4.8.2-2
ii  libgl1-mesa-glx [libgl1]  9.2.2-1
ii  libpulse0 4.0-6+b1
ii  libqt5core5   5.1.1+dfsg-5
ii  libqt5gui55.1.1+dfsg-5
ii  libqt5multimedia5 5.1.1-1
ii  libqt5network55.1.1+dfsg-5
ii  libqt5widgets55.1.1+dfsg-5
ii  libstdc++64.8.2-2

qgo recommends no packages.

Versions of packages qgo suggests:
ii  gnugo  3.8-6

-- 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#659191: kexec-tools: crashkernel boot messages not displayed, X11/gdm often not starting properly

[Linus Lüssing]

And one more update:

I was now able to get a working initrd output, yaiy :). This link [0]
got me on the right track, adding the i915 kernel module to the
initrd and therefore having an early Kernel-Mode-Setting helped. And
from then on, everything else, including X works great with the Intel
graphics driver.

So now just the issue with X, kexec and nouveau remains. And the
case where it is not possible for someone to add a recent
nouveau/i915/radeon module to the initrd.

Cheers, Linus


[0]: https://wiki.archlinux.org/index.php/Kernel_Mode_Setting#Early_KMS_start


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

Bug#659191: kexec-tools: crashkernel boot messages not displayed, X11/gdm often not starting properly

[Linus Lüssing]

Hi Khalid,

I was now able to redo my tests with the same Laptop and nvidia
device. And with the 3.10 kernel and more up to date Debian
Sid packages in general.

Unfortunately it's still not really working. It behaves
differently, but still isn't usable:

With the Damn Small Linux mentioned in my previous email, I'm
always getting a black screen with an underscore. I don't even get
the scrambled colours of the desktop.

When rebooting my current, fine working 3.10 kernel with kexec and
this command [0], the following happens:

The screen is blck during the initrd phase, I don't see the usual
cryptsetup password prompt. After typing the password blindly the
system continues booting and after the initrd phase the terminal
with the boot log and process actually shows up. I suspect that
the nouveau kernel modules have reset something at the moment.

However when it then continues to start X, I only get a black
screen with a white underscore again. But hey, I'm additionally
getting a visible, interactive mouse cursor :)! So it looks like
nouveau resets something, at least more than the Intel driver, but
not enough. And/Or kexec does not reset enough.

I can switch back to the terminal and that one still looks fine,
switching back to X and it's still just black, the underscore and
mouse cursor.

Also restarting gdm3 from the terminal does not help. Using
--reset-vga does not help either.

Cheers, Linus


[0]: kexec -l /boot/vmlinuz-3.10-2-amd64 --initrd=/boot/initrd.img-3.10-2-amd64 
--reuse-cmdline --reset-vga


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

Bug#659191: kexec-tools: crashkernel boot messages not displayed, X11/gdm often not starting properly

[Linus Lüssing]

Hi Khalid,

I currently have no nouveau compatible device at hand, but I
retried with this EEEPC and its Intel graphics device [0].
I just upgraded to the latest Linux kernel provided by Debian
unstable (3.10-2-amd64).

Unfortunately I'm still having graphics issues. First I tried
loading and rebooting my current kernel image and its initrd, but I'm
just having a black screen with a single line of text at the top
saying it is booting into the new kernel.

I've also tried this Damn Small Linux kernel[1]+initrd[2]
(it has all its content in the initrd, the initrd was created with
this guide [3]). The boot process is still black and the loaded
desktop is heavily scrambled but shows some colour and motion
(see [4],[5]). I was using this [6] kexec command. Also adding
--reset-vga does not help.

Booting the same DSL via kvm with this [7] command works without
any issues.

I'll retry with the nouveau device later this week, the original
laptop I was testing with back then still exists.

Thanks for all the feedback so far!

Cheers, Linus


[0]: 00:02.0 VGA compatible controller: Intel Corporation Atom Processor 
D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller (rev 02)
[1]: http://metameute.de/~tux/bugreport/debian/659191/linux24
[2]: http://metameute.de/~tux/bugreport/debian/659191/minirt24.gz
[3]: 
https://sites.google.com/site/sbobovyc/home/guides/other-linux/packing-dsl-into-initrd
[4]: http://metameute.de/~tux/bugreport/debian/659191/20130901_003.jpg
[5]: http://metameute.de/~tux/bugreport/debian/659191/20130901_004.jpg
[6]: kexec -l --command-line=ramdisk_size=10 init=/etc/init lang=us 
apm=power-off vga=789 initrd=minirt24.gz nomce noapic quiet BOOT_IMAGE=knoppix 
frominitrd nopcmcia noagp noswap base --initrd=./minirt24.gz ./linux24
[7]: kvm -kernel linux24 -initrd minirt24.gz -append ramdisk_size=10 
init=/etc/init lang=us apm=power-off vga=789 initrd=minirt24.gz nomce noapic 
quiet BOOT_IMAGE=knoppix frominitrd nopcmcia noagp noswap base


On Sat, Jan 12, 2013 at 02:48:40PM -0700, Khalid Aziz wrote:
 Hi Linus,
 
 There have been number of changes to the kexec code in the kernel
 including changes to reset PCI devices. Have you checked if you continue
 to see the graphics issue with nouveau driver?
 
 --
 Khalid
 


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

Bug#663690: kde-runtime: nepomukservicestup crash on startup

[Linus Lüssing]

Package: kde-runtime
Version: 4:4.8.4-1
Followup-For: Bug #663690

Hi,

I'm not sure whether it's the exact same error, but I'm also having a
segfault for nepomukservices:

---
$ dmesg | grep nepomukservices
[73111.855986] nepomukservices[3991]: segfault at 0 ip   (null) sp 
7fffd4023b68 error 14 in nepomukservicestub[40+7000]
[75766.773903] nepomukservices[12923]: segfault at 0 ip   (null) sp 
7fff9a012428 error 14 in nepomukservicestub[40+7000]
---

Cheers, Linus


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

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

Versions of packages kde-runtime depends on:
ii  kde-runtime-data4:4.8.4-1
ii  kdelibs5-plugins4:4.8.4-3
ii  libasound2  1.0.25-3
ii  libattica0  0.2.0-1
ii  libc6   2.13-34
ii  libcanberra00.28-4
ii  libexiv2-12 0.23-1
ii  libgcc1 1:4.7.1-3
ii  libjpeg88d-1
ii  libkcmutils44:4.8.4-3
ii  libkdeclarative54:4.8.4-3
ii  libkdecore5 4:4.8.4-3
ii  libkdesu5   4:4.8.4-3
ii  libkdeui5   4:4.8.4-3
ii  libkdewebkit5   4:4.8.4-3
ii  libkdnssd4  4:4.8.4-3
ii  libkemoticons4  4:4.8.4-3
ii  libkfile4   4:4.8.4-3
ii  libkhtml5   4:4.8.4-3
ii  libkidletime4   4:4.8.4-3
ii  libkio5 4:4.8.4-3
ii  libkmediaplayer44:4.8.4-3
ii  libknewstuff3-4 4:4.8.4-3
ii  libknotifyconfig4   4:4.8.4-3
ii  libkparts4  4:4.8.4-3
ii  libkpty44:4.8.4-3
ii  libnepomuk4 4:4.8.4-3
ii  libnepomukquery4a   4:4.8.4-3
ii  libntrack-qt4-1 016-1.1
ii  libopenexr6 1.6.1-6
ii  libphonon4  4:4.6.0.0-2
ii  libplasma3  4:4.8.4-3
ii  libpulse-mainloop-glib0 2.0-3
ii  libpulse0   2.0-3
ii  libqt4-dbus 4:4.8.2-1
ii  libqt4-declarative  4:4.8.2-1
ii  libqt4-network  4:4.8.2-1
ii  libqt4-script   4:4.8.2-1
ii  libqt4-svg  4:4.8.2-1
ii  libqt4-xml  4:4.8.2-1
ii  libqtcore4  4:4.8.2-1
ii  libqtgui4   4:4.8.2-1
ii  libqtwebkit42.2.1-4+b1
ii  libsmbclient2:3.6.6-2
ii  libsolid4   4:4.8.4-3
ii  libsoprano4 2.7.6+dfsg.1-1
ii  libssh-40.5.2-1
ii  libstdc++6  4.7.1-3
ii  libstreamanalyzer0  0.7.7-3
ii  libstreams0 0.7.7-3
ii  libx11-62:1.5.0-1
ii  libxcursor1 1:1.1.13-1
ii  oxygen-icon-theme   4:4.8.4-1
ii  perl5.14.2-12
ii  phonon  4:4.6.0.0-2
ii  plasma-scriptengine-javascript  4:4.8.4-1
ii  shared-desktop-ontologies   0.10.0-1

Versions of packages kde-runtime recommends:
ii  virtuoso-minimal  6.1.4+dfsg1-1

Versions of packages kde-runtime suggests:
pn  djvulibre-bin  none
ii  finger 0.17-15
pn  icoutils   none

-- debconf-show failed



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

Bug#681123: torify: Please add a paragraph in the WARNING section about identical identities

[Linus Lüssing]

Package: tor
Version: 0.2.3.19-rc-1
Severity: wishlist

When using multiple instances of torify on the same computer to connect to the
same host, it is possible for the according host to figure out that those two
clients are very likely the same.

While when specifically selecting a certain Tor proxy in an application,
I guess a user will very likely be aware that the same Tor identity is being
used.

However, for torify it is not that obvious that multiple instances are
_not_ necessarily using a new Tor identity. A user might think:

It's a new torify instance, so it's probably another one of this Tor
thingies, and they say a Tor thingy is pretty anonymous, right?
(Proxies? Ain't heard of that, know idea what that is - but torify works
great. What's torify doing internally? Don't know, I'm not a Tor
developer) I have read 'man torify' and it's not saying anything about
using the same Tor identity, it'd probably have been mentioned there otherwise.
So in conclusion, I guess each torify instance has to have its own,
anonymous identity.

Maybe for now a paragraph about every torify instance sharing the
same Tor identity should be added to the torify manpage in the WARNING
section?

Later, it'd be great if in fact each torify instance were having its own
identity, but don't know how difficult it is to implement that.

Cheers

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

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

Versions of packages tor depends on:
ii  adduser 3.113+nmu3
ii  libc6   2.13-34
ii  libevent-2.0-5  2.0.19-stable-3
ii  libssl1.0.0 1.0.1c-3
ii  lsb-base4.1+Debian7
ii  zlib1g  1:1.2.7.dfsg-13

Versions of packages tor recommends:
ii  logrotate3.8.1-4
ii  tor-geoipdb  0.2.3.19-rc-1
ii  torsocks 1.2-3

Versions of packages tor suggests:
pn  apparmor-utils none
pn  mixmaster  none
ii  privoxy3.0.19-2
ii  socat  1.7.1.3-1.4
pn  tor-armnone
pn  xul-ext-torbutton  none

-- Configuration Files:
/etc/tor/torrc changed [not included]

-- debconf-show failed



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

Bug#677416: uninstallable (missing Conflicts?)

[Linus Lüssing]

Package: wine-unstable
Version: 1.5.6-1
Followup-For: Bug #677416

Hi,

I can't install wine-unstable either. Most issues seem to be conflicts
with the wine package (1.4.1-1) I'm having installed, too. But
libsasl2*:i386 seems to yield conflicts (with its *:amd64 counter parts,
maybe?), too.

See attachment for detailed 'apt-get install wine-unstable' output.

Cheers, Linus

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

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

Versions of packages wine-unstable depends on:
ic  wine-bin-unstable  1.3.15-0.1

wine-unstable recommends no packages.

Versions of packages wine-unstable suggests:
pn  avscan | klamav | clamav   none
ii  binfmt-support 2.0.9
pn  ttf-mscorefonts-installer  none
pn  winbindnone
pn  wine-doc   none

-- debconf-show failed
$ sudo apt-get install wine-unstable
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  libldap-2.4-2:i386 libsasl2-2:i386 libsasl2-modules:i386 
libwine-alsa-unstable:i386 libwine-bin-unstable:i386 libwine-gl-unstable:i386
  libwine-ldap-unstable:i386 libwine-openal-unstable:i386 libwine-unstable:i386 
wine-bin-unstable:i386
Suggested packages:
  libsasl2-modules-otp:i386 libsasl2-modules-ldap:i386 
libsasl2-modules-sql:i386 libsasl2-modules-gssapi-mit:i386
  libsasl2-modules-gssapi-heimdal:i386 wine-doc:i386 libwine-cms-unstable:i386 
libwine-sane-unstable:i386 libwine-print-unstable:i386
  libwine-gphoto2-unstable:i386 wine-doc ttf-mscorefonts-installer winbind 
avscan klamav clamav
Recommended packages:
  ttf-liberation:i386
The following NEW packages will be installed:
  libldap-2.4-2:i386 libsasl2-2:i386 libsasl2-modules:i386 
libwine-alsa-unstable:i386 libwine-bin-unstable:i386 libwine-gl-unstable:i386
  libwine-ldap-unstable:i386 libwine-openal-unstable:i386 libwine-unstable:i386 
wine-bin-unstable:i386 wine-unstable
0 upgraded, 11 newly installed, 0 to remove and 12 not upgraded.
Need to get 0 B/21.8 MB of archives.
After this operation, 107 MB of additional disk space will be used.
Do you want to continue [Y/n]?
(Reading database ... 341598 files and directories currently installed.)
Unpacking libsasl2-2:i386 (from .../libsasl2-2_2.1.25.dfsg1-4+b1_i386.deb) ...
dpkg: error processing 
/var/cache/apt/archives/libsasl2-2_2.1.25.dfsg1-4+b1_i386.deb (--unpack):
 trying to overwrite shared '/usr/share/doc/libsasl2-2/changelog.Debian.gz', 
which is different from other instances of package libsasl2-2:i386
Selecting previously unselected package libldap-2.4-2:i386.
Unpacking libldap-2.4-2:i386 (from .../libldap-2.4-2_2.4.31-1_i386.deb) ...
Unpacking libsasl2-modules:i386 (from 
.../libsasl2-modules_2.1.25.dfsg1-4+b1_i386.deb) ...
dpkg: error processing 
/var/cache/apt/archives/libsasl2-modules_2.1.25.dfsg1-4+b1_i386.deb (--unpack):
 trying to overwrite shared 
'/usr/share/doc/libsasl2-modules/changelog.Debian.gz', which is different from 
other instances of package libsasl2-modules:i386
Unpacking libwine-unstable:i386 (from .../libwine-unstable_1.5.6-1_i386.deb) ...
dpkg: error processing 
/var/cache/apt/archives/libwine-unstable_1.5.6-1_i386.deb (--unpack):
 trying to overwrite '/usr/share/man/fr.UTF-8/man1/wineserver.1.gz', which is 
also in package libwine 1.4.1-1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Selecting previously unselected package libwine-alsa-unstable:i386.
Unpacking libwine-alsa-unstable:i386 (from 
.../libwine-alsa-unstable_1.5.6-1_i386.deb) ...
Unpacking libwine-bin-unstable:i386 (from 
.../libwine-bin-unstable_1.5.6-1_i386.deb) ...
dpkg: error processing 
/var/cache/apt/archives/libwine-bin-unstable_1.5.6-1_i386.deb (--unpack):
 trying to overwrite '/usr/share/man/man1/wineboot.1.gz', which is also in 
package libwine-bin:i386 1.4.1-1
Selecting previously unselected package libwine-gl-unstable:i386.
Unpacking libwine-gl-unstable:i386 (from 
.../libwine-gl-unstable_1.5.6-1_i386.deb) ...
Selecting previously unselected package libwine-ldap-unstable:i386.
Unpacking libwine-ldap-unstable:i386 (from 
.../libwine-ldap-unstable_1.5.6-1_i386.deb) ...
Selecting previously unselected package libwine-openal-unstable:i386.
Unpacking libwine-openal-unstable:i386 (from 
.../libwine-openal-unstable_1.5.6-1_i386.deb) ...
Unpacking wine-bin-unstable (from .../wine-bin-unstable_1.5.6-1_i386.deb) ...
dpkg: error processing 
/var/cache/apt/archives/wine-bin-unstable_1.5.6-1_i386.deb (--unpack):
 trying to overwrite '/usr/share/applications/winecfg.desktop', which is also 
in package wine-bin 1.4.1-1
Selecting previously unselected package wine-unstable.
Unpacking wine-unstable (from .../wine-unstable_1.5.6-1_amd64.deb) ...
Processing triggers for 

Bug#676955: xmonad: Add Provides: x-window-manager

[Linus Lüssing]

Package: xmonad
Version: 0.10-4+b2
Severity: wishlist

Hi,

It'd be nice if xmonad were listed in aptitude show x-window-manager
for instance and if it could provide a link for
'/usr/bin/x-window-manager' / '/etc/alternatives/x-window-manager' via
the alternatives system in Debian.

Cheers, Linus

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

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

Versions of packages xmonad depends on:
ii  libc6 2.13-33
ii  libffi5   3.0.10-3
ii  libgmp10  2:5.0.5+dfsg-2
ii  libx11-6  2:1.4.99.901-2
ii  libxext6  2:1.3.1-2
ii  libxinerama1  2:1.1.2-1
ii  x11-utils 7.7~1

Versions of packages xmonad recommends:
ii  libghc-xmonad-dev  0.10-4+b2
ii  libghc-xmonad-doc  0.10-4
ii  xfonts-base1:1.0.3

Versions of packages xmonad suggests:
ii  suckless-tools [dmenu]  38-1

-- debconf-show failed



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

Bug#675057: libwine-gl-unstable: OpenGL Performance issues on amd64: err:winediag:X11DRV_WineGL_InitOpenglInfo Direct rendering is disabled

[Linus Lüssing]

Package: libwine-gl-unstable
Version: 1.3.15-0.1
Severity: normal

Hi,

I'm seeing the following line in the output of wine:
---
err:winediag:X11DRV_WineGL_InitOpenglInfo Direct rendering is disabled
---

Which in some games affects the performance quite badly.

I could get rid of that error by:
* Following http://wiki.debian.org/Multiarch/HOWTO to install the i386
  architecture
* Installing libgl1-mesa-dri:i386 with aptitude
* Running wine like:
  LIBGL_DRIVERS_PATH=/usr/lib/i386-linux-gnu/dri/ wine [yourapp]

I guess steps like this might be handy having handled in the wine-unstable
install process automatically.

I'm on a 64bit system, both kernel- and userspace. I'm using the Open
Source nouveau graphics driver with a GeForce 8600M GT.

Cheers, Linus


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

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

Versions of packages libwine-gl-unstable depends on:
ii  ia32-libs 20120102
ii  libc6-i3862.13-32
ii  libwine-unstable  1.3.15-0.1

libwine-gl-unstable recommends no packages.

libwine-gl-unstable 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#675057: libwine-gl-unstable: OpenGL Performance issues on amd64: err:winediag:X11DRV_WineGL_InitOpenglInfo Direct rendering is disabled)

[Linus Lüssing]

PS: The full error line is:

---
err:winediag:X11DRV_WineGL_InitOpenglInfo Direct rendering is disabled, most 
likely your OpenGL drivers haven't been installed correctly
---

The issue might be similar to #566953. Maybe the steps posted
before might be a valid workaround for that issue, too.



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

Bug#674231: archivemount: Add 7zip support

[Linus Lüssing]

On Mon, May 28, 2012 at 03:31:08PM +0300, Nanakos Chrysostomos wrote:
 Dear Linus,

Hi Chris,

Thanks for your explanations. Hmm, are you sure Debian Sid has libarchive
2.8.5? I'm getting:
---
$ aptitude show libarchive12 | grep Version
Version: 3.0.4-1
---

And 3.0.4 seems to be the latest stable release of libarchive
according to libarchive.github.com.

And although libarchive 3.0.4 is supposed to support .7z archives, the
following commands do not work for me, the mount point remains empty:

---
$ mkdir /tmp/mytestdir/  \
mkdir /tmp/mytestdirmount  \
echo foobar  /tmp/mytestdir/testfile  \
7z a /tmp/mytestdir.7z /tmp/mytestdir  \
archivemount /tmp/mytestdir.7z /tmp/mytestdirmount  \
mount | grep archivemount  \
ls -lah /tmp/mytestdirmount

7-Zip [64] 9.20  Copyright (c) 1999-2010 Igor Pavlov  2010-11-18
p7zip Version 9.20 (locale=en_GB.UTF-8,Utf16=on,HugeFiles=on,2 CPUs)
Scanning

Creating archive /tmp/mytestdir.7z

Compressing  mytestdir/testfile  

Everything is Ok
archivemount on /tmp/mytestdirmount type fuse.archivemount 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
total 24K
drwxr-xr-x   0 linus linus 179 Jan  1  1970 .
drwxrwxrwt 105 root  root  24K May 30 04:02 ..
---


So I'm a little confused now, is this a missing feature in
archivemount (as I initially thought) or a bug in archivemount or
a bug in libarchive? Or a bug in front instead of inside of my laptop :)?

Cheers, Linus

 there is no problem if you already have installed libarchive version
 = 0.3.0. It supports .7z archives, so archivemount will handle such
 archives by default, no changes needed. Bare in mind that
 archivemount is a high-level wrapper for libarchive, so everything
 libarchive supports is supported also by archivemount.
 Wheezy/SID supports only libarchive-2.8.5-5 version for the moment.
 I believe that you should file a new bug to the libarchive
 maintainer to support the new version.
 
 
 Regards,
 Chris.
 
 
 On 05/24/2012 02:24 AM, Linus Lüssing wrote:
 Package: archivemount
 Version: 0.6.1-2+b1
 Severity: wishlist
 
 Hi,
 
 just tried using archivemount with a .7z archive, but it unfortunately
 didn't work, the mount point is empty.
 
 Before I tried archivemounting a .tar.xz which worked fine, but
 unfortunately also took a while on this 1GB+ archive.
 
 
 I'm not really into the details of compression algorithms and their
 container formats. But I'd guess that theoretically mounting a .7z
 archive should be much faster as the directory and file information are
 somehow more easily accesable, therefore not requiring to uncompress the
 whole archive before getting that information compared to .tar.xz, right?
 At least with 'ark' displaying the archive contents is instant with a
 .7z, while with the .tar.xz it again takes a while.
 
 As both .7z and .tar.xz use LZMA, the size of those two is pretty much
 the same. Therefore .7z could be a supperior solution to .tar.xz or
 .tar.lzma for archivemounting?
 
 Looks like .7z is supported by libarchive, too.
 
 Cheers, Linus
 
 
 -- System Information:
 Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
 Architecture: amd64 (x86_64)
 
 Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/bash
 
 Versions of packages archivemount depends on:
 ii  fuse  2.9.0-1
 ii  libarchive12  3.0.4-1
 ii  libc6 2.13-32
 ii  libfuse2  2.9.0-1
 
 archivemount recommends no packages.
 
 archivemount 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#674231: archivemount: Add 7zip support

[Linus Lüssing]

Package: archivemount
Version: 0.6.1-2+b1
Severity: wishlist

Hi,

just tried using archivemount with a .7z archive, but it unfortunately
didn't work, the mount point is empty.

Before I tried archivemounting a .tar.xz which worked fine, but
unfortunately also took a while on this 1GB+ archive.


I'm not really into the details of compression algorithms and their
container formats. But I'd guess that theoretically mounting a .7z
archive should be much faster as the directory and file information are
somehow more easily accesable, therefore not requiring to uncompress the
whole archive before getting that information compared to .tar.xz, right?
At least with 'ark' displaying the archive contents is instant with a
.7z, while with the .tar.xz it again takes a while.

As both .7z and .tar.xz use LZMA, the size of those two is pretty much
the same. Therefore .7z could be a supperior solution to .tar.xz or
.tar.lzma for archivemounting?

Looks like .7z is supported by libarchive, too.

Cheers, Linus


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

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

Versions of packages archivemount depends on:
ii  fuse  2.9.0-1
ii  libarchive12  3.0.4-1
ii  libc6 2.13-32
ii  libfuse2  2.9.0-1

archivemount recommends no packages.

archivemount 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#668402: okular fails to start, prints a bus error

[Linus Lüssing]

Hi,

Ok, I tried creating a new user and this one actually did not have
this problem. I also noticed, that /tmp/ksocket-$myuser and
/tmp/kde-$myuser did not exist, but for the new user they did.

I could fix this issue for me now by removing
/var/tmp/kdecache-$myuser. After that okular started fine again
and created those directories in /tmp/.

I made a backup of this not working directory in /var/tmp/
before deleting it. Would it be helpful to attach a tarball of
this directory here? Does this directory contain any sensible
information which I should not upload?

As this is/was a more general problem, not necessarily specific to
okular, should this bug be reassigned to some other package?

Cheers, Linus



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

Bug#669356: electricsheep unsuitable for Debian main?

[Linus Lüssing]

Package: electricsheep
Version: 2.7~b12+svn20091224-1.1
Severity: important

Hi,

Thanks for maintaining the electricsheep package in Debian. It works
great for me and I really love it. The idea behind it is great,
those animations are stunning!

However I'm currently wondering whether there might be issues with
the legal status of electricsheep and the Debian guidelines, maybe making
it unsuitable for Debian main. As I'm not certain and not that familiar
with the Debian legal side, I'd be curious about your thoughts on this.

What electricsheep currently does by default (correct me if I'm wrong):
* It downloads flam3 genome data and videos from a server.
* The machine generated flam3 data is CC-BY-NC, human generated flam3 data
  is CC-BY licensed, the video files are all CC-BY-NC licensed
  (according to http://electricsheep.org/reuse).
* Sometimes even non-CC, plainly copyrighted data is downloaded onto the
  machine and rendered according to the manpage
  (Some  jobs  rendered by the network [...]) and the website.

I'm wondering whether the following things are violations of Debian policies
(at least for Debian main):
* The downloaded, CC-BY-NC licensed data.
* The downloaded, plainly copyrighted data for the hidden extra
  rendering jobs.
* The hiden extra rendering jobs in general.
* The missing license information for the downloaded flam3 and video files
  (neither does the executable nor the Debian installation process
   enforce/inform about the CC license)
* Movies (ak. sheep) rendered and uploaded by the user are CC-BY-NC and
  attributed to Scott Draves and the Electric Sheep according to
  http://electricsheep.org/reuse - without neither the executable nor the
  Debian installation process ever asking for the user's consent to these
  license terms for movies rendered by this user.
* The one-sided CC-BY-NC enforcement (i.e. Scott Draves can use any
  electricsheep rendered by anyone for commercial purposes, but no one else
  effectively can - I know, according to his forum posts on electricsheep.org
  those sales are being used to keep electricsheep servers and development
  running and I believe him, that he's making use of this advantage in the
  best interest of the community and I definitely think he'd deserve an
  advantage like that for all his work on this awesome project, but
  unfortunately this process is again not transparent)


Let me know what you think, whether some of these points are valid or
not and what the implications for the electricsheep package in Debian
would be. If there are any valid issues making it non-compliant with
Debian main then I hope that we can sort these out as anything else
would be a loss for both the Debian and electricsheep project in my
opinion.


Cheers, Linus


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

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

Versions of packages electricsheep depends on:
ii  curl   7.25.0-1
ii  debconf [debconf-2.0]  1.5.42
ii  flam3  3.0.1-2.1
ii  gconf2 3.2.3-4
ii  libatk1.0-02.4.0-2
ii  libavcodec53   5:0.10.2-0.2
ii  libavformat53  5:0.10.2-0.2
ii  libavutil515:0.10.2-0.2
ii  libc6  2.13-27
ii  libcairo2  1.12.0-2
ii  libexpat1  2.1.0~beta3-2
ii  libfontconfig1 2.8.0-3.1
ii  libfreetype6   2.4.9-1
ii  libgdk-pixbuf2.0-0 2.26.0-2
ii  libglade2-01:2.6.4-1
ii  libglib2.0-0   2.32.0-3
ii  libgtk2.0-02.24.10-1
ii  libjpeg-progs  8d-1
ii  libpango1.0-0  1.30.0-1
ii  libxml22.7.8.dfsg-7
ii  mplayer3:1.0~rc4+svn20120324-0.0
ii  xloadimage 4.1-17
ii  zlib1g 1:1.2.6.dfsg-2

electricsheep recommends no packages.

electricsheep 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#669356: electricsheep unsuitable for Debian main?

[Linus Lüssing]

Hi Scott,

Thanks for your quick reply and directly taking part in this.

On Thu, Apr 19, 2012 at 10:03:26AM -0400, s...@draves.org wrote:
  Thanks Linus, glad you like it.
 
 I am not aware that Debian restricts the content that programs can
 download or calculate.  For example a regular web browser downloads
 copyrighted non-CC content all the time.  And it shows you ads in
 order to finance its development.  I would argue that our model is
 less intrusive, since the user is not disturbed or distracted at all.

Hmm, interesting point. I agree, embedding license information or ads
in the animations themselves would severly harm their beauty.

However as far as I know the electricsheep package currently heavily
relies on non-free content to function properly which could make
it unsuitable for Debian main. A web browser does not require
non-free content. I think it does not make a difference whether
such required content gets downloaded during runtime or whether it
was provided within the package. I'd guess that packages like
gnuvd-gnome or googleearth-package ended up in Debian contrib because
of similar reasons. Hmm, I'm CC'ing debian-legal as they should be
more familiar with the Debian policies than I am.

 
 But you are right, the package description could be more explicit
 (instead of just saying so in the man page).  How about adding this
 text:
 
 The videos downloaded and displayed by Electric Sheep are Creative
 Commons licensed (a mixture of CC-BY and CC-BY-NC).  Some jobs
 rendered by the network may be for images or animations which are not
 sheep at all, and will not appear in the screen-saver.  Some of these
 are used for commercial purposes in order to support the developers
 and servers that make the software.

Sounds better. But I think at least some information on how to
easily find the proper attribution for a specific sheep might be needed
to properly comply with the CC license. This should probably be
added to the manpage and Debian package's copyright file then as well,
I guess (which do not mention any Creative Commons licensing yet at all).
Maybe the complete attribution information might even need to get
downloaded together with the sheep, not sure how to interpret
section 4.b of the CC-BY license exactly.

@debian-legal: Is it enough to have this in a package description
/ copyright file or would a prompt during package installation be
needed? Is refering to an external website for the complete
attribution enough?

Hmm, I also had some more thoughts about the fifth point I made
(i.e. rendering/uploading under license terms the user did not
give consent to). My first thought was that the electricsheep
executable might need to ask for consent before uploading any of
this (similar like OpenStreetMap or Wikipedia ask for it when you
create an account there) to make the CC license enforceable and to
avoid any restrictive copyright claims and lawsuits from a user
who generated a sheep (= having rendered a movie). But on
second thought, I'm not sure anymore whether this is really
needed.

@debian-legal: Is the result of running an algorithm
copyrightable by the person who provided the CPU cycles in some
countries? Does it make a difference whether this algorithm is
deterministic, non-deterministic, distributed, user-parameterisable,
...?

By the way, is the rendering process deterministic or could someone
claim having contributed a creative input to the resulting,
rendered movie? Hmm, and now I'm also starting to wonder whether a
genome created by an algorithm can actually, legally be CC-BY-NC
licensed (which would otherwise be contrary to what
http://electricsheep.org/reuse claims).

If the rendered movies are not copyrightable by the renderer, then
my sixth point might be invalid as well due to
only applying to uploaded sheep genomes (the flam3 files), a
process which is not part of this package. But not sure, maybe the
sixth point might still be relevant due to a violation of the
Debian social contract's We will give back to the free software
community and Our priorities are our users and free software
as long as no publicly verifieable record of any financial
income going back to the community exists. And the No Discrimination
Against Fields of Endeavor clause in the Debian social contract,
of course.

For similar reasons, the non-transparent extra rendering jobs, point 3,
might be in violation of the Debian social contract, even if the user
gets properly notified about their presence. These jobs can be
deactivated via the --standalone switch, but this is not the
default and will make this package difficult to use for most
people. (Hmm, how difficult is it to add another switch to let a user
voluntarily activate contributing rendering cycles to
electricsheep.org for non-free jobs? How difficult is it to make
the correct enforcement of such an option verifiable by the user?)


Cheers, Linus

 
 ?
 
 
 On Thu, Apr 19, 2012 at 7:03 AM, Linus Lüssing linus.luess...@web.de wrote

Bug#668402: okular fails to start, prints a bus error

[Linus Lüssing]

Package: okular
Version: 4:4.7.4-2
Severity: important

Hi,

I'm currently having some issues with starting okular. I'm getting the
following error message:

---
$ okular
zsh: bus error  okular
---

The same happens for other KDE applications for me, like kcachegrind or
konqueror. amarok gives a similar error message saying:
---
Error message was:  org.freedesktop.DBus.Error.NoReply :  Message did not 
receive a reply (timeout by message bus) 
---

So it looks like something is wrong with my dbus?

Via googling I only found this one link:
http://ubuntuforums.org/showthread.php?t=1320876

But there didn't seem to be a solution other than reinstalling the whole
system...

Cheers, Linus


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

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

Versions of packages okular depends on:
ii  kde-runtime   4:4.7.4-2
ii  libc6 2.13-27
ii  libfreetype6  2.4.9-1
ii  libjpeg8  8d-1
ii  libkdecore5   4:4.7.4-4
ii  libkdeui5 4:4.7.4-4
ii  libkio5   4:4.7.4-4
ii  libkparts44:4.7.4-4
ii  libkprintutils4   4:4.7.4-4
ii  libkpty4  4:4.7.4-4
ii  libokularcore14:4.7.4-2
ii  libphonon44:4.6.0.0-1
ii  libpoppler-qt4-3  0.16.7-3
ii  libqca2   2.0.3-2
ii  libqimageblitz4   1:0.0.6-4
ii  libqt4-dbus   4:4.7.4-3
ii  libqt4-svg4:4.7.4-3
ii  libqt4-xml4:4.7.4-3
ii  libqtcore44:4.7.4-3
ii  libqtgui4 4:4.7.4-3
ii  libspectre1   0.2.6-1+b1
ii  libstdc++64.7.0-1
ii  phonon4:4.6.0.0-1
ii  zlib1g1:1.2.6.dfsg-2

okular recommends no packages.

Versions of packages okular suggests:
pn  ghostscript9.05~dfsg-4
pn  jovie  none
pn  okular-extra-backends  none
pn  poppler-data   0.4.5-2
pn  texlive-binaries   2011.20120328-1
pn  unrar  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#668156: RM: israndom -- RoQA; orphaned, low popcon, dead upstream

[Linus Lüssing]

Hi Moritz,

Thank you for your commitment in ensuring a certain quality
standard in software distributed via Debian.

However, I'm a little disappointed that the israndom package got
removed now. It worked pretty reliable for me, I love using it still
and as far as I know there is no alternative to it in the Debian
repositories. (big thanks to the former maintainer and developer,
Rudi!)

The only issue I was having with it was [1]. Which seems as far as
I can tell to have been introduced via your removal request of
libcomplearn-mod-lzmax and libcomplearn-mod-ppm back in Februrary/March 2011
[2],[3],[4] (at least installing these packages from Debian testing worked
flawlessly for me).

Could it be that libcomplearn-mod-lzmax and libcomplearn-mod-ppm
were wrongly, accidentally marked as Virtually unused/No revdeps,
maybe because israndom (and anycompress from the complearn-tools
package, too) was missing a Suggests (or maybe even a Recommends)
for them, making this relation less obvious?


So my question is, could those three packages be readded to
Debian unstable, with israndom (and complearn-tools) having a
Recommends or Suggests for the libcomplearn-mod-* added as
there aren't any issues with them (afaik) other than having no
maintainer?


Cheers, Linus

[1]: http://lists.debian.org/debian-qa-packages/2012/03/msg00185.html
[2]: http://packages.qa.debian.org/libc/libcomplearn-mod-lzmax.html
[3]: http://packages.qa.debian.org/libc/libcomplearn-mod-ppmd.html
[4]: http://bugs.debian.org/616378



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

Bug#667638: partprobe: Misses partitions with numbers 16

[Linus Lüssing]

Package: parted
Version: 2.3-9
Severity: normal

Hi,
GPT, 23 partitions).

I am currently having some trouble with partprobing a device created via
dmsetup. It basically consists of my normal /dev/sda with a few sectors
exchanged. My /dev/sda uses GPT and has more than 16 partitions.

Now doing a partprobe on the newly created /dev/mapper/testdisk only
creates a /dev/mapper/testdisk1 to /dev/mapper/testdisk16, the other ones
are missing.


The issue should be reproduceable with the attached test script. The
wget'ed or in this email attached raw disk image (32MB, 6KB compressed)
consists of 23 zero'ed 1MiB partitions with a GPT and fails this test script
for me.

I also tried upgrading parted/libparted0debian1 to 3.1, but the issue
still remained.


Cheers, Linus


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

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

Versions of packages parted depends on:
ii  libblkid1   2.20.1-4
ii  libc6   2.13-27
ii  libdevmapper1.02.1  2:1.02.67-2
ii  libparted0debian1   2.3-9
ii  libreadline66.2-8
ii  libtinfo5   5.9-5
ii  libuuid12.20.1-4

parted recommends no packages.

Versions of packages parted suggests:
pn  parted-doc  none

-- debconf-show failed
#!/bin/sh

NAME=testdisk

## Cleanup device mapper
for i in `seq 1 32`; do
	[ -e /dev/mapper/$NAME$i ]  {
		dmsetup remove $NAME$i
		[ -e /dev/mapper/$NAME$i ]  rm /dev/mapper/$NAME$i
	}
	[ -e /dev/mapper/${NAME}p$i ]  {
		dmsetup remove ${NAME}p$i
		[ -e /dev/mapper/${NAME}p$i ]  rm /dev/mapper/${NAME}p$i
	}
done
[ -e /dev/mapper/$NAME ]  dmsetup remove $NAME

## Cleanup loop device
LOOPDEV=`losetup -a | grep /tmp/$NAME | cut -f1 -d':'`
[ -n $LOOPDEV ]  losetup -d $LOOPDEV


## Setup loop device
wget -q http://x-realis.dyndns.org/parted/testdisk.xz -O - | xz -d  /tmp/$NAME
losetup -f /tmp/$NAME
LOOPDEV=`losetup -a | grep /tmp/$NAME | cut -f1 -d':'`

## Setup device mapper
echo 0 $((2**25/512)) linear $LOOPDEV 0 | dmsetup create $NAME


## Probe partition table
RETPARTPROBE=`partprobe -s /dev/mapper/$NAME`
echo $RETPARTPROBE
COUNTPARTPROBE=`echo $RETPARTPROBE | sed s#/dev/mapper/$NAME: gpt partitions## | wc -w`

ls /dev/mapper/$NAME*
COUNTLS=$((`ls /dev/mapper/$NAME* | wc -w`-1))

[ ! $COUNTLS -eq $COUNTPARTPROBE ]  {
	printf Failure! Partprobe missed some partitions (%d vs %d)\n $COUNTLS $COUNTPARTPROBE
	exit 1
}


printf Success! Partprobe found all %d partititions\n $COUNTLS
exit 0


testdisk.xz
Description: application/xz

Bug#667638: partprobe: Misses partitions with numbers 16

[Linus Lüssing]

PS: This is the output I'm getting from the previously attached
test script:

---
$ ./partprobe-test-more-than-16.sh
/dev/mapper/testdisk: gpt partitions 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 
18 19 20 21 22 23
/dev/mapper/testdisk /dev/mapper/testdiskp12  /dev/mapper/testdiskp16  
/dev/mapper/testdiskp5  /dev/mapper/testdiskp9
/dev/mapper/testdiskp1   /dev/mapper/testdiskp13  /dev/mapper/testdiskp2   
/dev/mapper/testdiskp6
/dev/mapper/testdiskp10  /dev/mapper/testdiskp14  /dev/mapper/testdiskp3   
/dev/mapper/testdiskp7
/dev/mapper/testdiskp11  /dev/mapper/testdiskp15  /dev/mapper/testdiskp4   
/dev/mapper/testdiskp8
Failure! Partprobe missed some partitions (16 vs 23)
---



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

Bug#664772: israndom: lzma/ppmd compression do not work: Error, cannot load compressor lzmax.

[Linus Lüssing]

Package: israndom
Version: 1.0.7-4
Severity: normal

Hi,

I am trying to figure out how to use the other compression methods. But
so far, only bzlib seems to work:

$ israndom -q -c bzlib some.rand
$ israndom -q -c lzma some.rand
Error, cannot load compressor lzma.
$ israndom -q -c lzmax some.rand
Error, cannot load compressor lzmax.
$ israndom -q -c ppmd some.rand
Error, cannot load compressor ppmd.
$ israndom -q -c ppmdx some.rand
Error, cannot load compressor ppmdx

I cannot find any suggestions in the manpage about what to do in this
case, so I guess it is a bug.


Cheers, Linus


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

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

Versions of packages israndom depends on:
ii  libc6  2.13-27
ii  libcomplearn1  1.1.7-1
ii  libglib2.0-0   2.30.2-6
ii  libgsl0ldbl1.15+dfsg-1
ii  libxml22.7.8.dfsg-7

israndom recommends no packages.

israndom 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#662869: ecryptfs-utils: Automounting fails on gdm3/kdm login: Could not update ICEauthority file

[Linus Lüssing]

Ok, I think I could fix the issue for me now. The ecryptfs modules
were missing in /etc/pam.d due to a modification of some of these
files I made ages ago. After checking twice that I wouldn't need
those changes anymore, the following command fixed it for me:
---
pam-auth-update --force
---

Most blog posts just assume that ecryptfs is set up correctly in
pam.d and googling for the ICEAuthority error message did not give
any useful results. Just one blog post (which was not mentioning
ICEAuthority) got me on the right track as it explicitly mentioned
the configuration of pam.d. And trying to reinstall ecryptfs-utils
then confirmed the PAM issues with the following error message:
---
pam-auth-update: Local modifications to /etc/pam.d/common-*, not updating.
pam-auth-update: Run pam-auth-update --force to override.
---

Maybe some sanity checks, maybe even a call to
pam-auth-update --package ecryptfs-utils, could be added to
ecrypts-migrate-home before doing any changes to the home
directory? For some people being locked out of their X session
could be scary even though ecryptfs-migrate-home makes a backup
and this lock-out could have been prevented.


Cheers, Linus

PS: Despite from this pam issue ecryptfs-migrate-home worked
flawlessly, thanks for this great script and ecryptfs in general!



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

Bug#659191: kexec-tools: crashkernel boot messages not displayed, X11/gdm often not starting properly

[Linus Lüssing]

On Tue, Feb 28, 2012 at 03:21:33PM -0700, Khalid Aziz wrote:
 That sounds like a kernel bug. Since kexec-tools loads the kexec kernel
 fine and the kexec kernel actually does start up, I would say
 kexec-tools is doing its job. What seems to be happening is the graphics
 driver is not shutting down graphics interface properly, so when the
 kexec'd kernel starts, framebuffer driver is unable to reinitialize the
 graphics controller. The X11 driver apparently is able to reinitialize
 the graphics controller some times and hence your screen is restored
 when gdm starts. This is a framebuffer driver issue which belongs in the
 kernel, not a kexec-tools bug.

Hi Khalid,

Hm, yes, looks like you are right. I have removed
xserver-xorg-video-nouveau and xserver-xorg-video-all and looking
at Xorg.0.log it seems to load vesa now
('Loading /usr/lib/xorg/modules/drivers/vesa_drv.so'). With the
vesa graphics driver I do not have this issue anymore and I see
the whole kernel boot process of the kexec'd kernel fine again.

Feel free to reassign this bug to the right package
(xserver-xorg-video-nouveau or one of the kernel packages?).

Thanks for having a look at this issue!

Cheers, Linus

PS: I can further confirm that the issue not only exists with my
make-kpkg kernel but also with the current, Debian provided
linux-image-3.2.0-2-amd64 package.

 
 -- 
 ===
 Khalid Aziz
 kha...@debian.org
 



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

Bug#662869: ecryptfs-utils: Automounting fails on gdm3/kdm login: Could not update ICEauthority file

[Linus Lüssing]

Package: ecryptfs-utils
Version: 95-1
Severity: important

Hi,

I've recently been trying to setup an encrypted home partition with
ecryptfs. However it does not quite seem to work for me so far. While
using ecryptfs-mount-private via a VT works, the automounting does not
and kdm/gdm3 therefore refuse a login with the following error message
after having typed in my password in the login screen of kdm/gdm3:

Could not update ICEauthority file [...]

And I'm forced to click a button to logout again.

I've created a minimal, new user account, just with an
adduser testuser and an ecryptfs-migrate-home -u testuser and I can
reproduce this issue with that one.

Also using gdm3 or kdm does not seem to make a difference.


For detailed steps and various outputs in between, see the attached
steps file and debug output files.

Please let me know if you need any additional information.


Cheers, Linus


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

Kernel: Linux 3.2.4 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages ecryptfs-utils depends on:
ii  gettext-base0.18.1.1-5
ii  keyutils1.5.5-1
ii  libc6   2.13-27
ii  libecryptfs095-1
ii  libgpg-error0   1.10-3
ii  libgpgme11  1.2.0-1.4
ii  libkeyutils11.5.5-1
ii  libnss3-1d  3.13.3-1
ii  libpam-runtime  1.1.3-7
ii  libpam0g1.1.3-7

ecryptfs-utils recommends no packages.

Versions of packages ecryptfs-utils suggests:
pn  cryptsetup2:1.4.1-2
pn  opencryptoki  none

-- no debconf information
## As root user

lsmod | grep ecryptfs  pre-lsmod
mount  pre-mount
df -h  pre-df-h
ls -lah /home  pre-ls-home

adduser testuser

ls -lah /home  2nd-ls-home

ecryptfs-migrate-home -u testuser

ls -lah /home /home/.ecryptfs /home/testuser /home/.ecryptfs/testuser/.ecryptfs 
 3rd-ls-home

/etc/init.d/gdm3 start

# logging in:
# Could not update ICEauthority file ...

# switching to VT, while keeping error message open
mount  mount-during
# (so still the same, ecryptfs not mounted)

# Clicking logout on error message, switching to VT again


## logging in as testuser on VT

ecryptfs-mount-private

ls -lah /home/testuser  4th-ls-home
mount  mount-after
# and ecryptfs-mount-private seems to work...
ecryptfs   81501  0 
udev on /dev type devtmpfs (rw,relatime,size=892316k,nr_inodes=223079,mode=755)
devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=179796k,mode=755)
/dev/mapper/sda1_crypt on / type ext4 
(rw,noatime,errors=remount-ro,user_xattr,acl,barrier=1,data=ordered)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime,size=359592k)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,relatime,size=359592k)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc 
(rw,nosuid,nodev,noexec,relatime)
/dev/mapper/sda5_crypt on /mnt/Temp3 type ext2 
(rw,relatime,errors=continue,user_xattr,acl)
/dev/mapper/sda23_crypt on /home type ext4 
(rw,relatime,user_xattr,barrier=1,data=ordered)
Filesystem   Size  Used Avail Use% Mounted on
rootfs77G   58G   19G  77% /
udev 872M 0  872M   0% /dev
tmpfs176M  708K  175M   1% /run
/dev/mapper/sda1_crypt77G   58G   19G  77% /
tmpfs5.0M 0  5.0M   0% /run/lock
tmpfs352M  4.6M  347M   2% /tmp
tmpfs352M   76K  352M   1% /run/shm
/dev/mapper/sda5_crypt14M  276K   13M   3% /mnt/Temp3
/dev/mapper/sda23_crypt   71G  1.2G   67G   2% /home
total 28K
drwxr-xr-x  4 root root 4.0K Mar  6 21:28 .
drwxr-xr-x 29 root root 4.0K Mar  6 21:03 ..
drwxr-xr-x  7 root root 4.0K Mar  6 21:28 bckp
drwx--  2 root root  16K Mar  6 06:14 lost+found
total 32K
drwxr-xr-x  5 root root 4.0K Mar  6 21:30 .
drwxr-xr-x 29 root root 4.0K Mar  6 21:03 ..
drwxr-xr-x  7 root root 4.0K Mar  6 21:28 bckp
drwx--  2 root root  16K Mar  6 06:14 lost+found
drwxr-xr-x  2 testuser testuser 4.0K Mar  6 21:30 testuser
/home:
total 40K
drwxr-xr-x  7 root root 4.0K Mar  6 21:31 .
drwxr-xr-x 29 root root 4.0K Mar  6 21:03 ..
drwxr-xr-x  7 root root 4.0K Mar  6 21:28 bckp
drwxr-xr-x  3 root root 4.0K Mar  6 21:31 .ecryptfs
drwx--  2 root root  16K Mar  6 06:14 lost+found
dr-x--  2 testuser testuser 4.0K Mar  6 21:31 testuser
drwx--  2 testuser testuser 4.0K Mar  6 21:30 testuser.UThEvke0

/home/.ecryptfs:
total 12K
drwxr-xr-x 3 root root 4.0K Mar  6 21:31 .
drwxr-xr-x 7 root root 4.0K Mar  6 

Bug#662084: libparted0debian1: False busy/mounted detection of some sdaX, X 16, partitions

[Linus Lüssing]

Package: libparted0debian1
Version: 2.3-8
Severity: normal


Hi,

Today I tried to create quite a few logical partitions and ended up
having 23 partitions in (g)parted in total.

Some of these, i.e. /dev/sda17 and /dev/sda19, were detected as mounted
and had the lock symbol next to it in gparted. I however could not
unmount and therefore could not delete this partition both within parted
or gparted.

Also a `ls /dev/sda*` or a `cat /proc/partitions` only showed a
/dev/sda1 to /dev/sda16:

---
$ cat /proc/partitions
major minor  #blocks  name

   80  625131864 sda
   81   81892356 sda1
   824914251 sda2
   83  1 sda3
   84  430013440 sda4
   85  16384 sda5
   86  16384 sda6
   87  16384 sda7
   88  16384 sda8
   89  16384 sda9
   8   10  16384 sda10
   8   11  16384 sda11
   8   12  16384 sda12
   8   13  16384 sda13
   8   14  16384 sda14
   8   15  16384 sda15
 2590  16384 sda16
---



parted 3.1 seems to work fine though. I could delete sda19 to sda23 with
it. And after having deleted those partitions funnilly sda17 to sda18
reappear within /dev and /proc/partitions:

---
$ cat /proc/partitions | grep sda
   80  625131864 sda
   81   81892356 sda1
   824914251 sda2
   83  1 sda3
   84  430013440 sda4
   85  16384 sda5
   86  16384 sda6
   87  16384 sda7
   88  16384 sda8
   89  16384 sda9
   8   10  16384 sda10
   8   11  16384 sda11
   8   12  16384 sda12
   8   13  16384 sda13
   8   14  16384 sda14
   8   15  16384 sda15
 2590  16384 sda16
 2591  16384 sda17
 2592  16384 sda18
---

After having used parted 3.1 and having those partitions reappear in the
kernel's partition table (Linux 3.2.4), parted 2.3.8 still does not work
though:

---
(parted) print
Model: ATA SAMSUNG HM640JJ (scsi)
Disk /dev/sda: 640GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End SizeType  File system  Flags
 1  32.3kB  83.9GB  83.9GB  primary
 2  83.9GB  88.9GB  5032MB  primary
 3  88.9GB  200GB   111GB   extended
 5  88.9GB  88.9GB  16.8MB  logical
 6  88.9GB  88.9GB  16.8MB  logical
 7  88.9GB  88.9GB  16.8MB  logical
 8  88.9GB  89.0GB  16.8MB  logical
 9  89.0GB  89.0GB  16.8MB  logical
10  89.0GB  89.0GB  16.8MB  logical
11  89.0GB  89.0GB  16.8MB  logical
12  89.0GB  89.0GB  16.8MB  logical
13  89.0GB  89.1GB  16.8MB  logical
14  89.1GB  89.1GB  16.8MB  logical
15  89.1GB  89.1GB  16.8MB  logical
16  89.1GB  89.1GB  16.8MB  logical
17  89.1GB  89.1GB  16.8MB  logical
 4  200GB   640GB   440GB   primary

(parted) rm 17
Error: Partition /dev/sda17 is being used. You must unmount it before you 
modify it with Parted.
---

Although it is definitely not mounted:
---
$ sudo mount
udev on /dev type devtmpfs (rw,relatime,size=892316k,nr_inodes=223079,mode=755)
devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=179796k,mode=755)
/dev/mapper/sda1_crypt on / type ext4 
(rw,noatime,errors=remount-ro,user_xattr,acl,barrier=1,data=ordered)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime,size=359592k)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
/dev/sdb1 on /boot type ext3 
(ro,noexec,noatime,nodiratime,errors=continue,barrier=1,data=ordered)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,relatime,size=359592k)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc 
(rw,nosuid,nodev,noexec,relatime)
$ df -h
Filesystem  Size  Used Avail Use% Mounted on
rootfs   77G   59G   18G  78% /
udev872M 0  872M   0% /dev
tmpfs   176M  612K  175M   1% /run
/dev/mapper/sda1_crypt   77G   59G   18G  78% /
tmpfs   5.0M 0  5.0M   0% /run/lock
tmpfs   352M  132K  352M   1% /tmp
/dev/sdb1   358M  304M   35M  90% /boot
tmpfs   352M  132K  352M   1% /run/shm
---

And the only swap partition is from /dev/sda2:
---
$ sudo dmsetup ls
sda1_crypt  (254, 1)
sda2_crypt  (254, 2)
$ cat /proc/swaps
FilenameTypeSizeUsedPriority
/dev/dm-2
---

So the busy detection seems to be wrong if I am not missing anything.


I am going to use the 3.1 parted build from now on and try to get my
initially planned setup working, I therefore might not be able to
reproduce this issue with other builds soonish if 

Bug#661522: xxxterm crashes when run via valgrind: Address 0x0 is not stack'd, malloc'd or (recently) free'd

[Linus Lüssing]

Package: xxxterm
Version: 1:1.10.0-1
Severity: normal

Hi,

I wanted to track down some memory issues I seemed to have with xxxterm
and tried using valgrind for that. However, xxxterm gets killed
with the following message as soon as I enter a website and
hit enter:
[...]
Address 0x0 is not stack'd, malloc'd or (recently) free'd
Process terminating with default action of signal 11 (SIGSEGV)
Access not within mapped region at address 0x0
[...]

I also tried setting a larger main stacksize of 115MB with
(can't set it any higher than 115MB) as valgrind suggested:
$ valgrind --main-stacksize=$((1024 * 1024 * 120)) xxxterm

But that does not seem to help either. I also tried the latest git
version (bfc73f8bbb339716392a3a85fb4c03ba2b1f984a) of xxxterm, as
well as removing the ulimits fiddling section in main(), but still the
same issue with valgrind.

Running xxxterm without valgrind does not crash though.

See the attached valgrind log output for details.


Cheers, Linus


valgrind: 1:3.7.0-2

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

Kernel: Linux 3.2.4 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages xxxterm depends on:
ii  libatk1.0-0 2.2.0-2
ii  libbsd0 0.3.0-2
ii  libc6   2.13-27
ii  libcairo2   1.10.2-6.2
ii  libfontconfig1  2.8.0-3.1
ii  libfreetype62.4.8-1
ii  libgcrypt11 1.5.0-3
ii  libgdk-pixbuf2.0-0  2.24.1-1
ii  libglib2.0-02.30.2-6
ii  libgnutls26 2.12.16-1
ii  libgtk2.0-0 2.24.10-1
ii  libjavascriptcoregtk-1.0-0  1.6.3-1
ii  libpango1.0-0   1.29.4-2
ii  libsoup2.4-12.36.1-1
ii  libwebkitgtk-1.0-0  1.6.3-1

xxxterm recommends no packages.

xxxterm suggests no packages.

-- no debconf information
==20729== Memcheck, a memory error detector
==20729== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==20729== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==20729== Command: xxxterm
==20729== 
xxxterm: config_parse: cannot open /home/linus/.xxxterm.conf: No such file or 
directory
==20729== Invalid read of size 4
==20729==at 0x7519C1E: ??? (in 
/usr/lib/i386-linux-gnu/libfontconfig.so.1.4.4)
==20729==by 0x751C339: FcConfigFilename (in 
/usr/lib/i386-linux-gnu/libfontconfig.so.1.4.4)
==20729==by 0x753059B: FcConfigParseAndLoad (in 
/usr/lib/i386-linux-gnu/libfontconfig.so.1.4.4)
==20729==by 0x7525505: FcInitLoadConfig (in 
/usr/lib/i386-linux-gnu/libfontconfig.so.1.4.4)
==20729==by 0x7525628: FcInitLoadConfigAndFonts (in 
/usr/lib/i386-linux-gnu/libfontconfig.so.1.4.4)
==20729==by 0x752589C: FcInit (in 
/usr/lib/i386-linux-gnu/libfontconfig.so.1.4.4)
==20729==by 0x751A494: FcConfigGetCurrent (in 
/usr/lib/i386-linux-gnu/libfontconfig.so.1.4.4)
==20729==by 0x751C0AF: FcConfigSubstituteWithPat (in 
/usr/lib/i386-linux-gnu/libfontconfig.so.1.4.4)
==20729==by 0x751C0F6: FcConfigSubstitute (in 
/usr/lib/i386-linux-gnu/libfontconfig.so.1.4.4)
==20729==by 0x7399479: ??? (in 
/usr/lib/i386-linux-gnu/libpangocairo-1.0.so.0.2904.0)
==20729==by 0x73666D7: ??? (in 
/usr/lib/i386-linux-gnu/libpangoft2-1.0.so.0.2904.0)
==20729==by 0x7367E86: ??? (in 
/usr/lib/i386-linux-gnu/libpangoft2-1.0.so.0.2904.0)
==20729==  Address 0xeac7dac is 20 bytes inside a block of size 22 alloc'd
==20729==at 0x48D0E2C: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==20729==by 0x7519B87: ??? (in 
/usr/lib/i386-linux-gnu/libfontconfig.so.1.4.4)
==20729==by 0x751C339: FcConfigFilename (in 
/usr/lib/i386-linux-gnu/libfontconfig.so.1.4.4)
==20729==by 0x753059B: FcConfigParseAndLoad (in 
/usr/lib/i386-linux-gnu/libfontconfig.so.1.4.4)
==20729==by 0x7525505: FcInitLoadConfig (in 
/usr/lib/i386-linux-gnu/libfontconfig.so.1.4.4)
==20729==by 0x7525628: FcInitLoadConfigAndFonts (in 
/usr/lib/i386-linux-gnu/libfontconfig.so.1.4.4)
==20729==by 0x752589C: FcInit (in 
/usr/lib/i386-linux-gnu/libfontconfig.so.1.4.4)
==20729==by 0x751A494: FcConfigGetCurrent (in 
/usr/lib/i386-linux-gnu/libfontconfig.so.1.4.4)
==20729==by 0x751C0AF: FcConfigSubstituteWithPat (in 
/usr/lib/i386-linux-gnu/libfontconfig.so.1.4.4)
==20729==by 0x751C0F6: FcConfigSubstitute (in 
/usr/lib/i386-linux-gnu/libfontconfig.so.1.4.4)
==20729==by 0x7399479: ??? (in 
/usr/lib/i386-linux-gnu/libpangocairo-1.0.so.0.2904.0)
==20729==by 0x73666D7: ??? (in 
/usr/lib/i386-linux-gnu/libpangoft2-1.0.so.0.2904.0)
==20729== 
==20729== Invalid read of size 4
==20729==at 0x7519C32: ??? (in 
/usr/lib/i386-linux-gnu/libfontconfig.so.1.4.4)
==20729==by 0x900642D: ??? (in /usr/lib/libwebkitgtk-1.0.so.0.11.2)
==20729==  Address 0xeacd428 is 16 bytes inside a block of 

Bug#536084: synaptics: Re: mouse trapped on second screen when using xinerama

[Linus Lüssing]

Package: xserver-xorg-input-synaptics
Followup-For: Bug #536084


Hi KiBi,

just to let you know, I've switched to nouveau and I guess also updated
Xorg from time to time and I'm not having this issue with the trapped
mouse anymore. So I'm not using nvidia-settings, but the command line
like:
---
xrandr --output VGA-1 --right-of LVDS-1 --mode 1024x768
---
And the synaptics mouse does not get stuck anymore.

I somehow have the feeling that switching to nouveau did the trick, but
not sure. Anyways, I'm really happy with it, I had no issues with
nouveau so far and even hardware accelerated 3D stuff works perfectly
fine with it - not just the mouse :). Yaiy, one more proprietory binary
b-s*** purged and gone for good!

Cheers, Linus

-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Feb  4 09:32 /etc/X11/X - /usr/bin/Xorg
-rwxr-xr-x 1 root root 1783236 Mar 26 08:55 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
01:00.0 VGA compatible controller [0300]: nVidia Corporation G84 [GeForce 8600M 
GT] [10de:0407] (rev a1)

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

KMS configuration files:

/etc/modprobe.d/i915-kms.conf:
  options i915 modeset=1
/etc/modprobe.d/radeon-kms.conf:
  options radeon modeset=1

Kernel version (/proc/version):
---
Linux version 2.6.38-2-amd64 (Debian 2.6.38-3) (b...@decadent.org.uk) (gcc 
version 4.4.5 (Debian 4.4.5-15) ) #1 SMP Thu Apr 7 06:43:20 UTC 2011

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 28435 Jul 30  2008 /var/log/Xorg.20.log
-rw-r--r-- 1 root root 31618 Mar  6 23:18 /var/log/Xorg.1.log
-rw-r--r-- 1 root root 32472 Jun 10 12:22 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[   237.919] 
X.Org X Server 1.9.5
Release Date: 2011-03-17
[   237.919] X Protocol Version 11, Revision 0
[   237.919] Build Operating System: Linux 2.6.32-5-amd64 i686 Debian
[   237.919] Current Operating System: Linux Linus-Debian 2.6.38-2-amd64 #1 SMP 
Thu Apr 7 06:43:20 UTC 2011 x86_64
[   237.919] Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.38-2-amd64 
root=/dev/mapper/sda1_crypt ro quiet
[   237.919] Build Date: 26 March 2011  07:50:38AM
[   237.919] xorg-server 2:1.9.5-1 (Cyril Brulebois k...@debian.org) 
[   237.919] Current version of pixman: 0.21.6
[   237.919]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   237.919] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   237.919] (==) Log file: /var/log/Xorg.0.log, Time: Fri Jun 10 10:27:57 
2011
[   237.997] (==) Using system config directory /usr/share/X11/xorg.conf.d
[   238.049] (==) No Layout section.  Using the first Screen section.
[   238.049] (==) No screen section available. Using defaults.
[   238.050] (**) |--Screen Default Screen Section (0)
[   238.050] (**) |   |--Monitor default monitor
[   238.051] (==) No monitor specified for screen Default Screen Section.
Using a default monitor configuration.
[   238.051] (==) Automatically adding devices
[   238.051] (==) Automatically enabling devices
[   238.137] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist.
[   238.137]Entry deleted from font path.
[   238.137] (WW) The directory /usr/share/fonts/X11/100dpi/ does not exist.
[   238.137]Entry deleted from font path.
[   238.137] (WW) The directory /usr/share/fonts/X11/75dpi/ does not exist.
[   238.137]Entry deleted from font path.
[   238.240] (WW) The directory /usr/share/fonts/X11/100dpi does not exist.
[   238.240]Entry deleted from font path.
[   238.240] (WW) The directory /usr/share/fonts/X11/75dpi does not exist.
[   238.240]Entry deleted from font path.
[   238.271] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/Type1,
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
built-ins
[   238.271] (==) ModulePath set to /usr/lib/xorg/modules
[   238.271] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[   238.271] (II) Loader magic: 0x81f9f60
[   238.271] (II) Module ABI versions:
[   238.271]X.Org ANSI C Emulation: 0.4
[   238.271]X.Org Video Driver: 8.0
[   238.271]X.Org XInput driver : 11.0
[   238.271]X.Org Server Extension : 4.0
[   238.272] (--) PCI:*(0:1:0:0) 10de:0407:1025:0121 rev 161, Mem @ 
0xf200/16777216, 0xd000/268435456, 0xf000/33554432, I/O @ 
0x2000/128
[   238.272] (II) Open ACPI successful (/var/run/acpid.socket)
[   238.272] (II) 

Bug#616610: openssh-client: ssh config does not like IPv6 link local address as hostname anymore (worked before today's update)

[Linus Lüssing]

Package: openssh-client
Version: 1:5.8p1-2
Severity: normal
Tags: sid ipv6

Hi everyone,

I did an aptitude full-upgrade today and since then an IPv6
specific functionality does not work anymore. I'm having an IPv6 link
local address in my ssh config file for a hostname:

## ~/.ssh/config ###
[...]
Host vm1
Hostname fe80::4:64ff:fea4:39b1%br0
User mesh-node
StrictHostKeyChecking no
IdentityFile ~/.ssh/vm_rsa
[...]


Since 1:5.8p1-2 I get the following error message:
$ ssh vm1
percent_expand: unknown key %b


This worked fine with openssh-client 1:5.5p1-6 before.

Cheers, Linus


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

Kernel: Linux 2.6.37-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages openssh-client depends on:
ii  adduser  3.112+nmu2  add and remove users and groups
ii  debconf [debconf-2.0 1.5.38  Debian configuration management sy
ii  dpkg 1.15.8.10   Debian package management system
ii  libc62.11.2-11   Embedded GNU C Library: Shared lib
ii  libedit2 2.11-20080614-2 BSD editline and history libraries
ii  libgssapi-krb5-2 1.8.3+dfsg-4MIT Kerberos runtime libraries - k
ii  libselinux1  2.0.96-1SELinux runtime shared libraries
ii  libssl0.9.8  0.9.8o-5SSL shared libraries
ii  passwd   1:4.1.4.2+svn3283-3 change and administer password and
ii  zlib1g   1:1.2.3.4.dfsg-3compression library - runtime

Versions of packages openssh-client recommends:
ii  openssh-blacklist 0.4.1  list of default blacklisted OpenSS
ii  openssh-blacklist-extra   0.4.1  list of non-default blacklisted Op
ii  xauth 1:1.0.5-1  X authentication utility

Versions of packages openssh-client suggests:
pn  keychain  none (no description available)
pn  libpam-sshnone (no description available)
pn  ssh-askpass   none (no description available)

-- 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#536084: mouse trapped on second screen when using xinerama

[Linus Lüssing]

On Wed, Jan 19, 2011 at 12:23:10AM +0100, Cyril Brulebois wrote:
 Linus Lüssing linus.luess...@web.de (22/11/2009):
  I'm still having this issue with, though I got a few steps further:
  Only my synaptics touchpad is affected. If I plug-in a USB-mouse,
  this one can freely move between the two screens (while the
  synaptics touchpad can't). I'll have a look soon, wheather
  xserver-xorg-input-synaptics 1.1.0-1, 1.1.1~git20090510-1 or 1.1.2-1
  broke it.
 
 Hi,
 
 any news about this? Is that still the case with the X stack from
 squeeze/sid, or with the one from experimental?
 
 KiBi.

Hi KiBi,

Oh wait what, was that really already one year ago - wow, time
passes quickly, hehe :).

Anyways, I tried the current version from Debian unstable today (1.2.2-2),
and it's still the same issue. The synaptics touchpad can't escape the
main screen, a usb mouse can. I'm installing v1.3 now from experimental
and will try that tomorrow when I have a second screen available again.

Cheers, Linus



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

Bug#577244: gnome-terminal: segmentation fault, crash on startup

[Linus Lüssing]

Package: gnome-terminal
Version: 2.30.0-1
Severity: important
Tags: sid

I did an aptitude full-upgrade yesterday and since then I'm not able to
start gnome-terminal anymore, getting a segmentation fault instead.
2.28.2-1 worked fine before. Don't know if this is of any help, but
that's what I'm getting with valgrind for the Debian version:
--
==6000== Memcheck, a memory error detector
==6000== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
==6000== Using Valgrind-3.5.0-Debian and LibVEX; rerun with -h for copyright 
info
==6000== Command: gnome-terminal
==6000==
Xlib:  extension RANDR missing on display :0.0.
==6000== Invalid read of size 4
==6000==at 0x7802C0B: cairo_xlib_surface_get_width (in 
/usr/lib/libcairo.so.2.10800.10)
==6000==by 0x6D70A2D: ??? (in /usr/lib/libvte.so.9.13.0)
==6000==by 0x6D73853: ??? (in /usr/lib/libvte.so.9.13.0)
==6000==by 0x6D596A9: ??? (in /usr/lib/libvte.so.9.13.0)
==6000==by 0x6D67590: ??? (in /usr/lib/libvte.so.9.13.0)
==6000==by 0x8069223: ??? (in /usr/bin/gnome-terminal)
==6000==by 0x73F4C9B: g_cclosure_marshal_VOID__VOID (in 
/usr/lib/libgobject-2.0.so.0.2400.0)
==6000==by 0x73E57A8: ??? (in /usr/lib/libgobject-2.0.so.0.2400.0)
==6000==by 0x73E7141: g_closure_invoke (in 
/usr/lib/libgobject-2.0.so.0.2400.0)
==6000==by 0x73FCE99: ??? (in /usr/lib/libgobject-2.0.so.0.2400.0)
==6000==by 0x73FEBD3: g_signal_emit_valist (in 
/usr/lib/libgobject-2.0.so.0.2400.0)
==6000==by 0x73FF055: g_signal_emit (in /usr/lib/libgobject-2.0.so.0.2400.0)
==6000==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==6000==
==6000==
==6000== Process terminating with default action of signal 11 (SIGSEGV)
==6000==  Access not within mapped region at address 0x0
==6000==at 0x7802C0B: cairo_xlib_surface_get_width (in 
/usr/lib/libcairo.so.2.10800.10)
==6000==by 0x6D70A2D: ??? (in /usr/lib/libvte.so.9.13.0)
==6000==by 0x6D73853: ??? (in /usr/lib/libvte.so.9.13.0)
==6000==by 0x6D596A9: ??? (in /usr/lib/libvte.so.9.13.0)
==6000==by 0x6D67590: ??? (in /usr/lib/libvte.so.9.13.0)
==6000==by 0x8069223: ??? (in /usr/bin/gnome-terminal)
==6000==by 0x73F4C9B: g_cclosure_marshal_VOID__VOID (in 
/usr/lib/libgobject-2.0.so.0.2400.0)
==6000==by 0x73E57A8: ??? (in /usr/lib/libgobject-2.0.so.0.2400.0)
==6000==by 0x73E7141: g_closure_invoke (in 
/usr/lib/libgobject-2.0.so.0.2400.0)
==6000==by 0x73FCE99: ??? (in /usr/lib/libgobject-2.0.so.0.2400.0)
==6000==by 0x73FEBD3: g_signal_emit_valist (in 
/usr/lib/libgobject-2.0.so.0.2400.0)
==6000==by 0x73FF055: g_signal_emit (in /usr/lib/libgobject-2.0.so.0.2400.0)
==6000==  If you believe this happened as a result of a stack
==6000==  overflow in your program's main thread (unlikely but
==6000==  possible), you can try to increase the size of the
==6000==  main thread stack using the --main-stacksize= flag.
==6000==  The main thread stack size used in this run was 8388608.
==6000==
==6000== HEAP SUMMARY:
==6000== in use at exit: 1,201,347 bytes in 14,389 blocks
==6000==   total heap usage: 42,919 allocs, 28,530 frees, 4,175,181 bytes 
allocated
==6000==
==6000== LEAK SUMMARY:
==6000==definitely lost: 4,392 bytes in 15 blocks
==6000==indirectly lost: 14,460 bytes in 719 blocks
==6000==  possibly lost: 790,896 bytes in 7,473 blocks
==6000==still reachable: 391,599 bytes in 6,182 blocks
==6000== suppressed: 0 bytes in 0 blocks
==6000== Rerun with --leak-check=full to see details of leaked memory
==6000==
==6000== For counts of detected and suppressed errors, rerun with: -v
==6000== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 156 from 11)
zsh: segmentation fault  valgrind gnome-terminal
--

Then I started to try compiling version 2.30.0 manually with a
./configure  make. The make failed because of a missing
scrollkeeper-config. Installing rarian-compat then did the trick for
making the compiling procedure work (shouldn't the ./configure check for
the scrollkeeper-config script?).

Running this self-compiled version resulted in a similar error, but
valgrind giving some extra information for the failing function in
gnome-terminal now:

--
==10519== Memcheck, a memory error detector
==10519== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
==10519== Using Valgrind-3.5.0-Debian and LibVEX; rerun with -h for copyright 
info
==10519== Command: ./gnome-terminal
==10519==
Xlib:  extension RANDR missing on display :0.0.

** (gnome-terminal:10519): WARNING **: Could not load desktop file 
'/usr/local/share/applications/gnome-terminal.desktop': No such file or 
directory
Failed to load UI: Failed to open file 
'/usr/local/share/gnome-terminal/terminal.xml': No such file or directory

(gnome-terminal:10519): Gtk-CRITICAL **: gtk_box_pack: assertion 

Bug#577244: gnome-terminal: segmentation fault, crash on startup

[Linus Lüssing]

 Already fixed:
 
 vte (1:0.24.0-2) unstable; urgency=low
 .
* 01_transparent_crash.patch: patch by Tetralet to fix a crash when
  the background file is missing, or when the transparent background
  has no root window. Closes: #576624.
Awesome, yes, works again. Thanks for the quick fix :).

Cheers, Linus


signature.asc
Description: Digital signature

Bug#568341: cryptsetup: password not recognised anymore since update of initramfs

[Linus Lüssing]

Hi Jonas,

Damn it, again I've been doing too many steps at the same time to
reliably say what fixed it...
Updating console-setup to 1.53, purging and reinstalling the
linux-image, setting KEYMAP=y in initramfs.conf (it was somehow
set to 'n'), then updating initramfs. Et voilà, then the
boottime.kmap.gz was there again! I'm very sure that I've tried
the same procedure before except the console-setup before... but,
ehm... nevermind, seems to work now again :).

Thanks for the patience.

Cheers, Linus


signature.asc
Description: Digital signature

Bug#568341: cryptsetup: password not recognised anymore since update of initramfs

[Linus Lüssing]

Okay, had a closer look at it now. I found out, that the keyboard
layout seems to be wrong when I want to type my password. In the
upcoming busybox of the broken initrd-images, the layout is the
english layout, while on the working backup, it is still the
German one. Looks like there is no /etc/boottime.kmap.gz in the
my updated/broken initrd-images. Any idea how that one could get
lost lately and how I could fix this?

Cheers, Linus


signature.asc
Description: Digital signature

Bug#568342: cryptsetup: password not recognised anymore since update of initramfs

[Linus Lüssing]

Sorry, had a problem with my mailserver, this one is a duplicate
of #568341. Therefore, this one here, #568342, can be closed.

Cheers, Linus


signature.asc
Description: Digital signature

Bug#505439: Fails to build under amd64

[Linus Lüssing]

Package: kqemu-source
Version: 1.4.0~pre1-3
Severity: normal

Hi,

I'm still having trouble building kqemu on an 2.6.31-1-amd64 kernel
here. But for me, the error message looks quite different; see
attachment for details.

Cheers, Linus

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.31-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages kqemu-source depends on:
ii  bzip2 1.0.5-4high-quality block-sorting file co
ii  debhelper 7.4.12 helper programs for debian/rules
ii  dpatch2.0.31 patch maintenance system for Debia
ii  make  3.81-7 An utility for Directing compilati

Versions of packages kqemu-source recommends:
ii  module-assistant  0.11.3 tool to make module package creati

kqemu-source suggests no packages.

-- no debconf information
dpatch  deapply-all  
rm -rf patch-stamp patch-stampT debian/patched
dh_testdir
#dh_testroot
# Cleaning package
/usr/bin/make clean
make[1]: Entering directory `/usr/src/modules/kqemu'
/usr/bin/make -C common clean
make[2]: Entering directory `/usr/src/modules/kqemu/common'
rm -f *.o *~ monitor-image.h genoffsets genmon monitor_def.h \
   monitor-image.bin monitor-image.out \
   i386/*.o x86_64/*.o
make[2]: Leaving directory `/usr/src/modules/kqemu/common'
rm -f kqemu.ko *.o *~
make[1]: Leaving directory `/usr/src/modules/kqemu'
dh_clean
/usr/bin/make  -f debian/rules clean
make[1]: Entering directory `/usr/src/modules/kqemu'
dpatch  deapply-all  
rm -rf patch-stamp patch-stampT debian/patched
dh_testdir
#dh_testroot
# Cleaning package
/usr/bin/make clean
make[2]: Entering directory `/usr/src/modules/kqemu'
/usr/bin/make -C common clean
make[3]: Entering directory `/usr/src/modules/kqemu/common'
rm -f *.o *~ monitor-image.h genoffsets genmon monitor_def.h \
   monitor-image.bin monitor-image.out \
   i386/*.o x86_64/*.o
make[3]: Leaving directory `/usr/src/modules/kqemu/common'
rm -f kqemu.ko *.o *~
make[2]: Leaving directory `/usr/src/modules/kqemu'
dh_clean
make[1]: Leaving directory `/usr/src/modules/kqemu'
/usr/bin/make  -f debian/rules kdist_clean kdist_config binary-modules
make[1]: Entering directory `/usr/src/modules/kqemu'
dpatch  deapply-all  
rm -rf patch-stamp patch-stampT debian/patched
dh_testdir
#dh_testroot
# Cleaning package
/usr/bin/make clean
make[2]: Entering directory `/usr/src/modules/kqemu'
/usr/bin/make -C common clean
make[3]: Entering directory `/usr/src/modules/kqemu/common'
rm -f *.o *~ monitor-image.h genoffsets genmon monitor_def.h \
   monitor-image.bin monitor-image.out \
   i386/*.o x86_64/*.o
make[3]: Leaving directory `/usr/src/modules/kqemu/common'
rm -f kqemu.ko *.o *~
make[2]: Leaving directory `/usr/src/modules/kqemu'
dh_clean
/usr/bin/make -w -f debian/rules clean
make[2]: Entering directory `/usr/src/modules/kqemu'
dpatch  deapply-all  
rm -rf patch-stamp patch-stampT debian/patched
dh_testdir
#dh_testroot
# Cleaning package
/usr/bin/make clean
make[3]: Entering directory `/usr/src/modules/kqemu'
/usr/bin/make -C common clean
make[4]: Entering directory `/usr/src/modules/kqemu/common'
rm -f *.o *~ monitor-image.h genoffsets genmon monitor_def.h \
   monitor-image.bin monitor-image.out \
   i386/*.o x86_64/*.o
make[4]: Leaving directory `/usr/src/modules/kqemu/common'
rm -f kqemu.ko *.o *~
make[3]: Leaving directory `/usr/src/modules/kqemu'
dh_clean
make[2]: Leaving directory `/usr/src/modules/kqemu'
make[1]: Nothing to be done for `kdist_config'.
for templ in ; do \
cp $templ `echo $templ | sed -e 's/_KVERS_/2.6.31-1-amd64/g'` ; \
  done
for templ in `ls debian/*.modules.in` ; do \
test -e ${templ%.modules.in}.backup || cp ${templ%.modules.in} ${templ%.modules.in}.backup 2/dev/null || true; \
sed -e 's/##KVERS##/2.6.31-1-amd64/g ;s/#KVERS#/2.6.31-1-amd64/g ; s/_KVERS_/2.6.31-1-amd64/g ; s/##KDREV##/2.6.31-2/g ; s/#KDREV#/2.6.31-2/g ; s/_KDREV_/2.6.31-2/g  '  $templ  ${templ%.modules.in}; \
  done
dh_testroot
dh_prep
# Build the module
./configure --kernel-path=/lib/modules/2.6.31-1-amd64/build
Source path   /usr/src/modules/kqemu
C compilergcc
Host C compiler   gcc
make  make
host CPU  x86_64

kernel sources/lib/modules/2.6.31-1-amd64/build
kbuild type   2.6
/usr/bin/make
make[2]: Entering directory `/usr/src/modules/kqemu'
make -C common all
make[3]: Entering directory `/usr/src/modules/kqemu/common'
gcc -Wall -O2 -Werror -g -D__KERNEL__ -I.. -o genoffsets genoffsets.c
./genoffsets  monitor_def.h
gcc -D__KERNEL__ -nostdinc -iwithprefix include -I. -I.. -D__ASSEMBLY__ -c -o x86_64/nexus_asm.o x86_64/nexus_asm.S
x86_64/nexus_asm.S: Assembler messages:
x86_64/nexus_asm.S:42: Error: bad register name 

Bug#568341: cryptsetup: password not recognised anymore since update of initramfs

[Linus Lüssing]

Package: cryptsetup
Version: 2:1.1.0~rc2-1
Severity: important

No key available with this passphrase.
cryptsetup: cryptsetup failed, bad password or options?

This problem first occured when I upgraded  my kernel from
linux-image-2.6.32-trunk-amd64 2.6.32-4 - 2.6.32-5
on 18th of January with aptitude. After that, the 2.6.32 kernel did not
recognise my password anymore (and yes, I'm very sure that I didn't
misstype it as I tried it on different days and always this one failed
while 2.6.31-1-amd64 still worked).
Now I did a update-initramfs -k all -u  update-grub2 today and now
the 2.6.31 does not recognise my password anymore as well. However, the
initrd.img-2.6.31-1-amd64.bak still works perfectly fine.

I uploaded the broken and the working versions here:
http://krtek.asta.uni-luebeck.de:8080/~tux/bugreport/initrd.img-2.6.31-1-amd64
http://krtek.asta.uni-luebeck.de:8080/~tux/bugreport/initrd.img-2.6.31-1-amd64.working
(sorry my mailserver couldn't cope with those large files, that's why I
didn't attach them here directly)

Thanks for the help.

Cheers, Linus

-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-2.6.31-1-amd64 root=/dev/mapper/sda1_crypt ro quiet

-- /etc/crypttab
sda1_crypt /dev/sda1 none luks

-- /etc/fstab
# /etc/fstab: static file system information.
#
# file system mount point   type  options   dump  pass
proc/proc   procdefaults0   0
/dev/mapper/sda1_crypt /   ext3noatime,errors=remount-ro 0  
 1
/dev/mapper/sda2_crypt none swap sw 0 0
#UUID=2aca1436-8f11-4980-94bb-727f7c42aa7c   /boot   ext3
noatime,nodiratime,ro,suid,dev,noexec,auto,async0   0
UUID=a0261c67-e563-4546-9f07-218f2293ed7a   /boot   ext3
noatime,nodiratime,ro,suid,dev,noexec,auto,async0   0
/dev/hda/media/cdrom0   udf,iso9660 user,noauto 0   0
81.163.130.102:/vol/fast/mnt/cccnfs nfs user0   0

-- lsmod
Module  Size  Used by
nvidia   9611288  30 
ppdev   7272  0 
lp 10708  0 
parport38304  2 ppdev,lp
sco11092  2 
bridge 48192  0 
stp 2900  1 bridge
bnep   13824  2 
rfcomm 36080  5 
kvm_intel  46456  0 
kvm   160824  1 kvm_intel
acpi_cpufreq8912  0 
cpufreq_powersave   1824  0 
cpufreq_conservative 7856  0 
cpufreq_userspace   3652  0 
cpufreq_stats   4692  0 
l2cap  21216  20 bnep,rfcomm
nfsd  269392  9 
exportfs4656  1 nfsd
nfs   264496  0 
lockd  68356  2 nfsd,nfs
fscache41496  1 nfs
nfs_acl 3296  2 nfsd,nfs
auth_rpcgss40960  2 nfsd,nfs
sunrpc198664  10 nfsd,nfs,lockd,nfs_acl,auth_rpcgss
fuse   60288  1 
dm_snapshot23228  0 
dm_mirror  14792  0 
dm_region_hash 12736  1 dm_mirror
dm_log 10052  2 dm_mirror,dm_region_hash
batman_adv 63140  0 
firewire_sbp2  15552  0 
loop   16060  0 
snd_hda_codec_realtek   260452  1 
snd_hda_intel  27656  0 
snd_hda_codec  76064  2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep   8328  1 snd_hda_codec
arc42080  2 
ecb 3104  2 
snd_pcm_oss37456  0 
snd_mixer_oss  15216  1 snd_pcm_oss
snd_pcm79976  3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq_midi7008  0 
snd_rawmidi23264  1 snd_seq_midi
iwlagn 86384  0 
snd_seq_midi_event  7744  1 snd_seq_midi
iwlcore   112128  1 iwlagn
snd_seq51456  3 snd_seq_midi,snd_seq_midi_event
uvcvideo   57372  0 
snd_timer  21984  2 snd_pcm,snd_seq
snd_seq_device  7508  3 snd_seq_midi,snd_rawmidi,snd_seq
snd64584  12 
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
videodev   37296  1 uvcvideo
i2c_i801   10432  0 
soundcore   8160  1 snd
mac80211  139808  2 iwlagn,iwlcore
v4l1_compat12964  2 uvcvideo,videodev
acer_wmi   17064  0 
v4l2_compat_ioctl32 9920  1 videodev
btusb  12884  2 
psmouse42396  0 
serio_raw   5972  0 
bluetooth  56404  9 sco,bnep,rfcomm,l2cap,btusb
button  6544  0 
cfg80211   89832  3 iwlagn,iwlcore,mac80211
processor  40316  3 acpi_cpufreq
wmi 7520  1 acer_wmi
evdev  10608  19 
pcspkr  2976  0 
i2c_core   24448  3 nvidia,videodev,i2c_i801
snd_page_alloc  9952  2 

Bug#536084: mouse trapped on second screen when using xinerama

[Linus Lüssing]

Package: xserver-xorg
Version: 1:7.4+4
Severity: normal

I'm still having this issue with, though I got a few steps further: Only
my synaptics touchpad is affected. If I plug-in a USB-mouse, this one
can freely move between the two screens (while the synaptics touchpad
can't). I'll have a look soon, wheather xserver-xorg-input-synaptics
1.1.0-1, 1.1.1~git20090510-1 or 1.1.2-1 broke it.

Cheers, Linus

-- Package-specific info:
/var/lib/x11/X.roster does not exist.

/var/lib/x11/X.md5sum does not exist.

X server symlink status:
lrwxrwxrwx 1 root root 13 Mar  2  2008 /etc/X11/X - /usr/bin/Xorg
-rwxr-xr-x 1 root root 1689944 Oct 13 13:31 /usr/bin/Xorg

/var/lib/x11/xorg.conf.roster does not exist.

VGA-compatible devices on PCI bus:
01:00.0 VGA compatible controller: nVidia Corporation G84 [GeForce 8600M GT] 
(rev a1)

/var/lib/x11/xorg.conf.md5sum does not exist.

Xorg X server configuration file status:
-rw-r--r-- 1 root root 2486 Nov 14 16:21 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 1.0  (bui...@murphy)  Sat Aug 22 07:54:25 UTC 2009

Section ServerLayout
Identifier Layout0
Screen  0  Screen0 0 1200
Screen  1  Screen1 Above Screen0
InputDeviceKeyboard0 CoreKeyboard
#InputDeviceMouse0 CorePointer
EndSection

Section Files
EndSection

Section ServerFlags
Option Xinerama 1
EndSection

#Section InputDevice
## generated from default
#Identifier Mouse0
#Driver mouse
#Option Protocol auto
#Option Device /dev/psaux
#Option Emulate3Buttons no
#Option ZAxisMapping 4 5
#EndSection

Section InputDevice
# generated from default
Identifier Keyboard0
Driver kbd
EndSection

Section Monitor
# HorizSync source: edid, VertRefresh source: edid
Identifier Monitor0
VendorName Unknown
ModelName  LPL
HorizSync   30.0 - 75.0
VertRefresh 60.0
Option DPMS
EndSection

Section Monitor
# HorizSync source: edid, VertRefresh source: edid
Identifier Monitor1
VendorName Unknown
ModelName  LG 901B
HorizSync   30.0 - 98.0
VertRefresh 50.0 - 160.0
Option DPMS
EndSection

Section Device
Identifier Device0
Driver nvidia
VendorName NVIDIA Corporation
BoardName  GeForce 8600M GT
BusID  PCI:1:0:0
Screen  0
EndSection

Section Device
Identifier Device1
Driver nvidia
VendorName NVIDIA Corporation
BoardName  GeForce 8600M GT
BusID  PCI:1:0:0
Screen  1
EndSection

Section Screen
Identifier Screen0
Device Device0
MonitorMonitor0
DefaultDepth24
Option TwinView 0
Option metamodes DFP: 1280x800 +0+0; DFP: 1024x768 +0+0; DFP: 
800x600 +0+0; DFP: 640x480 +0+0
SubSection Display
Depth   24
EndSubSection
EndSection

Section Screen
Identifier Screen1
Device Device1
MonitorMonitor1
DefaultDepth24
Option TwinView 0
Option metamodes CRT: 1600x1200 +0+0
SubSection Display
Depth   24
EndSubSection
EndSection



Xorg X server log files on system:
-rw-r--r-- 1 root root 28435 Jul 30  2008 /var/log/Xorg.20.log
-rw-r--r-- 1 root root 16909 May 13  2009 /var/log/Xorg.1.log
-rw-r--r-- 1 root root 20693 Nov 22 12:38 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file
/var/log/Xorg.0.log:

X.Org X Server 1.6.5
Release Date: 2009-10-11
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.30.8-dsa-ia32 i686 Debian
Current Operating System: Linux Linus-Debian 2.6.31-1-amd64 #1 SMP Sun Nov 15 
22:05:44 UTC 2009 x86_64
Build Date: 13 October 2009  11:25:51AM
xorg-server 2:1.6.5-1 (bui...@murphy.debian.org) 
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /var/log/Xorg.0.log, Time: Sun Nov 22 12:35:00 2009
(==) Using config file: /etc/X11/xorg.conf
(==) ServerLayout Layout0
(**) |--Screen Screen0 (0)
(**) |   |--Monitor Monitor0
(**) |   |--Device Device0
(**) |--Screen Screen1 (1)
(**) |   |--Monitor Monitor1
(**) |   |--Device Device1
(**) |--Input Device Keyboard0
(**) Option Xinerama 1
(==) Automatically adding devices
(==) Automatically enabling devices
(**) Xinerama: enabled
(WW) The directory /usr/share/fonts/X11/cyrillic does not exist.
Entry deleted from font path.
(==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,

Bug#544773: Update to cryptsetup 2:1.0.7-2 breaks booting

[Linus Lüssing]

Package: cryptsetup
Version: 2:1.0.7-2
Severity: normal

Yes, I'm having the same problem here. I updated cryptsetup yeseterday to
2:1.07-2 and now I can't boot my usual 2.6.30-1-amd64 anymore.
My other kernels on this machine seem unaffected, just my usual
kernel-image does not boot. So I can select/boot 2.6.30-1-686,
2.6.29-2-amd64 or 2.6.29-2-686 with grub-pc for example.

Cheers, Linus

-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-2.6.30-1-686 root=/dev/mapper/sda1_crypt ro quiet

-- /etc/crypttab
sda1_crypt /dev/sda1 none luks

-- /etc/fstab
# /etc/fstab: static file system information.
#
# file system mount point   type  options   dump  pass
proc/proc   procdefaults0   0
/dev/mapper/sda1_crypt /   ext3noatime,errors=remount-ro 0  
 1
/dev/sda4   /boot   ext3defaults0   2
/dev/hda/media/cdrom0   udf,iso9660 user,noauto 0   0

-- lsmod
Module  Size  Used by
ppdev   6348  0 
lp  8012  0 
parport31144  2 ppdev,lp
sco 8832  2 
bridge 39968  0 
stp 2112  1 bridge
bnep   10860  2 
rfcomm 30368  5 
kvm_intel  39744  0 
kvm   138608  1 kvm_intel
acpi_cpufreq7640  0 
cpufreq_powersave   1292  0 
cpufreq_conservative 6256  0 
cpufreq_userspace   2768  0 
cpufreq_stats   3520  0 
l2cap  18120  20 bnep,rfcomm
fuse   47752  1 
dm_snapshot21604  0 
dm_mirror  12580  0 
dm_region_hash 10668  1 dm_mirror
dm_log  8464  2 dm_mirror,dm_region_hash
firewire_sbp2  12692  0 
loop   13324  0 
snd_hda_codec_realtek   178472  1 
joydev  8576  0 
arc41560  2 
snd_hda_intel  22192  0 
ecb 2368  2 
snd_hda_codec  63580  2 snd_hda_codec_realtek,snd_hda_intel
iwlagn 72244  0 
snd_hwdep   6120  1 snd_hda_codec
snd_pcm_oss32232  0 
snd_mixer_oss  12368  1 snd_pcm_oss
iwlcore92264  1 iwlagn
snd_pcm62420  3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq_midi5688  0 
acer_wmi   14700  0 
snd_rawmidi18596  1 snd_seq_midi
rfkill  9668  5 iwlcore,acer_wmi
psmouse37528  0 
serio_raw   4560  0 
snd_seq_midi_event  6212  1 snd_seq_midi
snd_seq42436  2 snd_seq_midi,snd_seq_midi_event
btusb  10276  2 
wmi 6184  1 acer_wmi
uvcvideo   49308  0 
mac80211  142848  2 iwlagn,iwlcore
snd_timer  17436  2 snd_pcm,snd_seq
snd_seq_device  6136  3 snd_seq_midi,snd_rawmidi,snd_seq
i2c_i8018564  0 
i2c_core   20844  1 i2c_i801
processor  34504  3 acpi_cpufreq
snd49060  11 
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
battery 6012  0 
videodev   31040  1 uvcvideo
soundcore   6184  1 snd
v4l1_compat11416  2 uvcvideo,videodev
bluetooth  47060  9 sco,bnep,rfcomm,l2cap,btusb
cfg80211   6  3 iwlagn,iwlcore,mac80211
evdev   8028  12 
button  5060  0 
ac  2960  0 
snd_page_alloc  8180  2 snd_hda_intel,snd_pcm
ext3  107172  2 
jbd41036  1 ext3
mbcache 6924  1 ext3
sha256_generic 11216  0 
aes_i5868092  2 
aes_generic27436  1 aes_i586
cbc 3012  1 
dm_crypt   11092  1 
dm_mod 49992  6 dm_snapshot,dm_mirror,dm_log,dm_crypt
ide_cd_mod 24484  0 
cdrom  30316  1 ide_cd_mod
ata_generic 4340  0 
ide_pci_generic 3632  0 
sd_mod 28748  3 
crc_t10dif  1632  1 sd_mod
piix5680  0 
ahci   30068  2 
libata150904  2 ata_generic,ahci
tg391244  0 
libphy 19552  1 tg3
firewire_ohci  18952  0 
firewire_core  37736  2 firewire_sbp2,firewire_ohci
crc_itu_t   2148  1 firewire_core
sdhci_pci   6540  0 
sdhci  14868  1 sdhci_pci
mmc_core   46384  1 sdhci
led_class   3852  3 iwlcore,acer_wmi,sdhci
ricoh_mmc   3464  0 
ide_core   88100  3 ide_cd_mod,ide_pci_generic,piix
scsi_mod  131800  3 firewire_sbp2,sd_mod,libata
uhci_hcd   19132  0 
ehci_hcd   29680  0 
usbcore   126004  5